1. Trying to delete one resource doesn't work Deleting all resources does work as a work around.
2. Their is a max size of records ( I don't remember what it was.) It is the READ_SIZE variable in SyncManager.java.
I have never had a problem were the conduit would not be called. The conduit manager calls jsync13.dll that in turns calls the java conduit.
The direct benefit of using java is the VAST number of classes that can be accessed. There are http classes, image classes, etc that make the manipulation
of data from the palm easy. Before the flames begin, I know that you can do that in C++ (my day job). However, java makes the development of
sophisticated conduits that aren't simply copying of data to the desktop computer easy.
The jsync stuff is now quite old. Clearly palm has decided its not that important. I think the hope was that with a java conduit the developer could have a cross platform
(read mac) conduit. Not so!
So, using java for conduits really is a catch-22. Though it is easier to extend the conduits capabilities, there appears to be no development on the platform.
I would suggest to palm to make the source for the jsync13.dll available to us developers. Why not open the source of a library that isn't being actively
developed?
Chris
Henk Jonas wrote:
[EMAIL PROTECTED] wrote:
I can't seem to find any information about the development of jsync. Will
there ever be a jdk 1.4 compatable version? Is there a date set for this?
Does anyone recommend any alternatives?
I have been using jsync for quite a while but I just upgraded my db
software and now it is not 1.3 compatable so I am in a bit of a conondrum.
thanks
-ryan
I would suggest to switch to a conduit written in C++. In my opinion, the jsync-stuff has no benefits over conduits in C++. But you have a 10 MByte installation and sometimes weird effect, like your conduit not called etc.
Henk
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
