In article <[EMAIL PROTECTED]>, Mickael Remond <[EMAIL PROTECTED]> wrote:
> Wojtek wrote: > > Hi, > > > > > > As I found JabberD 1.4.* is licensed under GNU GPL. > > > > If i will make an external component (jabber:component:accept one > > according to JEP-0114) for logging messages does it fall into > > "derivative work" category of GPL? If so, the component should be > > opened source under GPL (or other OSI compatible license). Am I wrong? > > In my opinion, it depend of the nature of your module. This is true if > your module is strongly linked (library bound to the code). If the > module is communicating through a network socket using the XML protocol, > I think you can provide a proprietary implementation. This is correct. External components can have any license you want. > > Another question. Can commercial apllications communicate through > > JabberD 1.4.* without any license restrictions? > > Yes. If it were not the case, you would not be able to use > infrastructure software through the network and would have a problem > with GPL STMP server (you could not send mail with Outlook for exemple) > or with FTP server (You could not use a proprietary software to upload > files). > So, I think there is no problem. Correct. Peter _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
