|
From: Robert J. L. <leb...@fi...> - 2002-05-14 00:29:47
|
> It seems to me that the client can be J2ME or J2SE, as long as we > package them separately. Server side, of course, has to be J2SE. But > we need a framework supporting HTTP, WSP and OBEX. So that takes some > domain expertise to figure out a robust server side architecture. > Just an odd question..... I haven't worked with the j2me apis yet, however last summer I worked with the SuperWaba classes, and developed a few things like ant scripts, etc. for them. I tried looking for a jar file comparable to the ejb.jar, is there a j2me.jar somewhere at java.sun.com? > In sync4j, HTTP transport is usable as of now, but then since the protocol > implementation is not ready i.e. reply with a meaningful xml doc according > to the spec, so that's why I said the protocol hasn't been fully > implemented. > > If you want something immediately usable, try ksync.enhydra.org. sync4j > is still at its infancy and yearns for some parents to bring it up. :) > I like the Enhydra stuff, but they change their licenses to suit their moods... I dropped instantdb for that exact reason. Rob |