Re: FastCGI licensing contact

On 31/08/06, Weslee Bilodeau <weslee.bilodeau-NEGAmrGOAmuW9VltB2KXpZqQE7yCjDx5@public.gmane.org> wrote:
>
> Saju Pillai wrote:
> > Greetings,
> >
> >   We would like to ship FastCGI devkit client/server as part of a
> > commercial product with some modifications. These modifications will
> > break compatibility between opensource fastcgi implementations and our
> > version (which is fine with us). The regular fcgi clients/servers will
> > not be able to talk to the modified servers/clients - and we think such
> > a change requires endorsement from the fcgi license owner(s). We have
> > been unsuccessful in our attempts to contact the fcgi license owners.
> > Can someone on the list help us locate them please.
>
> Just off hand, but I don't see why you need them to endorse your product?
>
> Provided you follow the public specification, it shouldn't matter.



You mean the FCGI protocol spec ? We are not going to follow this spec and
intend to rewire the server<->client communication using some in
house/custom protocols.



If your breaking the devkit API thats one thing, and not really a big
> deal. APIs vary. My company wrote our own based off the specification
> thats nothing like the devkit API.



Actually we would like to retain the API, infact we would really like to be
binary compatible with the fcgi-devkit/client-lib clients though we are
willing to drop compatibility if it is too painful to maintain.

We really love the idea of *native* (as in not running in a j2ee/whatever
container) persistent process supplying web-content and this is the concept
that we want to  (:)) from fastcgi.


We didn't ask for anyones endorsement, as I'm sure the various perl,
> python, PHP, .Net, C#, Delphi, etc kits didn't.
>
> If your breaking the specification then you break compatibility with all
> existing web servers, which in my opinion would make the kit useless?



We own the clients and the servers which will use this implementation. If we
are able to maintain binary compatibility with the devkit client library
then relinking a client against our client lib should work.

regards
srp

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/