On Tuesday 05 March 2002 17:57, Peter M. Jansson wrote:
> The short version is that if you create a derived work, you must allow
> access to the source of your derived work. If used AOLserver code and
> hacked it to specialize it somehow, then your hacks must be available. If
> your product only uses AOLserver as a program, and only interfaces with it
> through the network and via modules, then you do not have to provide the
> sources for the programs that organize AOLserver for you, nor for the
> modules.
>
> Keep in mind that if you really did modify the AOLserver code and need to
> be able to distribute it, you can negotiate an alternative license with
> AOL, but they'd be under no obligation to make the alternative license free
> for you or your customers.
Thanks for the explanation, Peter.
The point is, I did some changes to the core server and
this is something I can post on the SourceForge or provide
to the aolserver community by some other means w/o any
problems whatsoever. I'm only afraid that this stuff is so
application-special that most of the people wouldn't need them at all.
I've included (a small summary):
o. ns_atstartup command to run scripts when the server is starting
o. fixed a bug in parsing headers which enables me to do keepalive
post's in addition to get's
o. added a small controller process which kicks the server again
if it exists with error (I know, daemontools... but I needed
a nice wrapped thing for simple installation)
and such kind of stuff. If I post those patches to the SF project,
what do I have to provide (and if) then ?
I'm sure somebody from the AOL team could say a word about this.
Thanks,
Zoran
