Not sure what this question has to do with
licensing but, here goes.

a) For over 15 years InterBase used /etc/services
to listen on port 3050 which then has 'inetd'
spawn a gds_inet_server (a connection/engine)
to perform database work. Perhaps I do not
understand everything involved but, I do not
believe that inetd is pooling anything. Once
the gds_inet_server is spawned 'inetd' is no
longer involved and tcp sockets managed the
traffic between client and server. Is my
understanding correct? And also, why is this
deemed unacceptable in an 'enterprise' environment?

b) We have implemented SuperServer, the multithreaded
engine, on platforms that we felt had a good
enough threading package. We are currently
investigating SuperServer for Linux.

Markus



Ryan Mills wrote:

>
> From: "Ryan Mills" <rmills@...>
>
> This could be a FAQ, but Interbase is using "inetd" to pool connections
> yeah? This is clearly unacceptable in an enterprise environment, when or
> rather is there a push to make this a multithreaded server? The website
> says this is the case, but without source, how can my engineers contribute
> to make this so?
>
> With regards,
>
> RM
>
> ----- Original Message -----
> From: "Andy Gibson" <andy@...>
> To: <IB-Architect@onelist.com>
> Sent: Wednesday, March 22, 2000 7:11 AM
> Subject: [IB-Architect] Re : License Question
>
> > From: "Andy Gibson" <andy@...>
> >
> > Hi all,
> >
> > I realise that this is an IB architect group, but had a quick question.
>
> ------------------------------------------------------------------------
> Special Offer-Earn 300 Points from MyPoints.com for trying @Backup
> Get automatic protection and access to your important computer files.
> Install today:
> http://click.egroups.com/1/2344/3/_/_/_/953708033/
> ------------------------------------------------------------------------
>
> To unsubscribe from this group, send an email to:
> IB-Architect-unsubscribe@onelist.com