From: Armin B. <arm...@de...> - 2005-07-12 09:20:25
|
Helge Hess wrote: > On Jul 8, 2005, at 21:45, Armin Bauer wrote: > >> i just finished setting up the libsyncml project space at >> http://libsyncml.opensync.org. > > > Is this library suitable for server side implementations as well or is > it focused on clients? > The library consists of several layers. The lowest layers are the transport like http client, http server, obex client etc The next layer is responisble for parsing the data and dispatching them. The highest layers consists of objects which can be registered with a session at a specific path. At the moment there are: - a authentication object that receives incoming SyncHdrs and authenticates the user if necessary - a devinf object - a syncml Ds server which implements the server part of the ds protocol and which receives commands like alert, sync, map etc - a syncml ds client which implements the client part of ds (not yet implemented) so the library will be usable as both server and client by using different parts of the library >> And i also got the libsyncml project at sf.net donated by Max. Thanks >> for this. > > > Personally I would be surprised if Max had something against relicensing > the code under LGPL if its currently under GPL. > I agree with the others that this would be quite important. > the only thing i used is the libsyncml project space, not the code. So far all code in the libsyncml library is writen by myself. I choose the GPL for a simple reason: I dont want that the library is used for a commercial product without the duty to return something to the community which could either be open sourcing their own code (so that i can be linked against GPL code) or by buying a commercial license. Just out of curiosity, is there anything that would _require_ a LGPL license or is it just that the GPL is too restrictive? > Greets, > Helge |