[OJB-developers] Newlines and Client/Server

[<Joa...@tp...>]

Hy,

finally I come to the stage where I stop flaming and start doing real work.
At the moment I have got two TODOs; both are non-intrusive and require no
special knowledge of the OJB-internals (thus they are perfect for me ;-).

First of all I'd like to resolve the Newline-Problem (I don't know if
anyone else runs into it, but i'd like to fix it nevertheless). I've taken
a closer look at the script-tool in the hsqldb-Repository and it seems that
the problem is that it uses windows-newlines hardcoded (instead of
system-dependent newlines). This is no problem for java itself (it
interprets all legal newlines on all platforms, even mixed) but when you
check it into CVS from a unix platform, but using windows-newlines, CVS
assumes that you allready give it unix-newlines, and thus completely f*cks
up the newlines when you check it out again on windows. I'm going to
contact the hsqldb-Maintainer regarding this issue and try to give him a
patch for this ('though I doubt, that he will release a new version just
for this patch, unless of course he has enough patches otherwise).

The other problem is, that we'd love to use the C/S-concept of of
ObjectBridge, but have rather specific network-restrictions (HTTP/HTTPS at
most). So, we'd need to wrap the PersistenceBrokerServer into a Servlet.
Basically this is no problem (from what I saw it seems that the
functionality is seperated quite good). Obviously I'd also need some minor
modifications to the PersistenceBrokerClient. Now I'd like to know if you'd
prefer it if I modified those files to support both (only about 15-30 lines
of changes in each of them, I guess) or if should copy them and do my
modifications on new Classes. (or even do some refactoring, but I have to
look into it, if it would even be necessary).

One more problem also has to do with C/S: there doesn't seem to be any kind
of authentification and/or encryption support in it. Both of them would be
fairly easy, once they have the ability to use Servlets as the Server.

Btw, has the C/S-concept been optimized with regards to bandwidth/latency?
At the first glance it seem that it is intended to be used primarily in a
LAN.

regards
Joachim Sauer