Re: [Epp-rtk-devel] Keeping EPP sessions alive

[Rick H W. <we...@ar...>]

Dan,

I have been working on a pool for epp and I have both .info and .biz in
production using this code. I'm not happy with it though. I am working on
a superclass of EPPClient that has a higher level API that will be pooled
insted of the EPPClient class.

I wanted to add it to the distrib in november but I just have been working
on other things. I also wrote an MBean for jboss with the pooling stuff
for RRP and EPP its real cool but not for public consumption...

praticly speaking I should just post an example of the pooling stuff and
let others do the integration, i'm just too over worked to finish it up in
a timely mannor.

i'll see if i can't get an example pool out by xmas.

-rick



On 19 Dec 2001, Daniel Manley wrote:

> oh, yeah, sorry.  The RTK doesn't have any connection pooling
> functionality or auto-keepalive stuff.  Rick, were you developing
> something to do this a while back?  Maybe it could be included in the
> RTK package.
>
> Dan
>
>
> On Wed, 2001-12-19 at 14:23, alan wrote:
> > That's the technique I intend to use- build a preforking proxy server
> > which accepts EPP connections from the rest of our registration
> > system, and sends "poll" commands periodically when each registry
> > connection is inactive.  I just wanted to make sure there wasn't an
> > easier way :)
> >
> > As far as I know, preforking servers typically support a fourth
> > parameter as well- the absolute minimum number of connections.  This
> > is typically higher than the minimum free connections, to make sure
> > that the server starts up enough connections when it is first
> > launched.
> >
> > Thanks!
> >
> > Alan
> >
> > On 19 Dec 2001, Daniel Manley wrote:
> >
> > > The general practice is to open connections and keep them alive.  It
> > > relatively expensive to establish an SSL/TLS connection and doing in
> > > real time with a request from a client would not be advisable.
> > >
> > > A good practice to adopt would be to imitate apache's server model.
> > > Start up with a few connections and through handling requests, keep the
> > > number of free connections to busy connections balanced.  I think three
> > > numbers are involved:  min free connections, max free connections, and
> > > max overall connections.  (a connection is roughly equal to a thread,
> > > depending on your implementation) A server or proxy would be constantly
> > > adjusting to varying loads... opening new connections in times of higher
> > > load and closing connection in quiet periods.
> > >
> > > Dan
> > >
> > > On Wed, 2001-12-19 at 14:00, alan wrote:
> > > > Hello.
> > > >
> > > > Registrars have historically had problems making connections to the
> > > > Verisign registry at certain times of the day due to extreme
> > > > overusage.  Because of this, everyone typically grabs a bunch of
> > > > connections and holds on to them as long as possible, reconnecting
> > > > only when Absolutely Necessary.
> > > >
> > > > Is this a problem with Neulevel and Afilias at this point?  I've heard
> > > > recommendations for these registrars to keep your connections open as
> > > > long as possible in any case, for efficiency (to avoid setting up and
> > > > tearing down all those TCP connections).  Do the existing EPP toolkits
> > > > deal with this for you, or do they just require the end programmer to
> > > > periodically send a 'poll' command if they want to keep a connection
> > > > open?  If they do deal with it, what technique is used?
> > > >
> > > > Thanks!
> > > >
> > > > Alan
> >
> >
> > _______________________________________________
> > Epp-rtk-devel mailing list
> > Epp...@li...
> > https://lists.sourceforge.net/lists/listinfo/epp-rtk-devel
>
>
>
> _______________________________________________
> Epp-rtk-devel mailing list
> Epp...@li...
> https://lists.sourceforge.net/lists/listinfo/epp-rtk-devel
>