Socket Pools?

[Jacob]

Is there any tutorials or documentation that you could point me towards
regarding pooling requests for a limited number of sockets?

I want users of this class to be able to request a socket and if one isn't
available, their request will be queued and a socket returned when it is
available. Consequently, if a socket is no longer in use, how to return it
to the pool. This is all in an attempt to not make so many connections to a
particular port, but use one if it has already been established.

Does anybody know what I'm talking about?

Any help is appreciated.

Thanks,
Jacob

[Glenn Wilson]

I would have a look at threading to control the sockets.
Get the users to use a UDP Port to request a Connection, when this
connection is successful send back a UDP Message withthe connection detail
for a TCP Port to connect to (Also Send a Hash value say the IP Address and
port as well as some secret Code, to be used to verify that the incomming
connection is allowed to connect at this time)
"Jacob" <[e-mail]> wrote in message
news:6ndRc.4869$Lj.426@fed1read03...

Is there any tutorials or documentation that you could point me towards
regarding pooling requests for a limited number of sockets?

I want users of this class to be able to request a socket and if one isn't
available, their request will be queued and a socket returned when it is
available. Consequently, if a socket is no longer in use, how to return it
to the pool. This is all in an attempt to not make so many connections to a particular port, but use one if it has already been established.

Does anybody know what I'm talking about?

Any help is appreciated.

Thanks,
Jacob

[William Stacey [MVP]]

Almost but not really. You talkin about clients sending requests or a
server that listens for incomming socket connections?
--
wjs mvp

"Jacob" <[e-mail]> wrote in message
news:6ndRc.4869$Lj.426@fed1read03...

Is there any tutorials or documentation that you could point me towards
regarding pooling requests for a limited number of sockets?

I want users of this class to be able to request a socket and if one isn't
available, their request will be queued and a socket returned when it is
available. Consequently, if a socket is no longer in use, how to return it
to the pool. This is all in an attempt to not make so many connections to a particular port, but use one if it has already been established.

Does anybody know what I'm talking about?

Any help is appreciated.

Thanks,
Jacob

[Jacob]

Clients sending requests....

Just looking for a really smart way to manage the requests/sockets. (If the
analogy helps, think of it like a SQL connection pool, but for sockets).

Thanks,
Jacob

"William Stacey [MVP]" <st*****@mvps.org> wrote in message
news:%2***************@TK2MSFTNGP12.phx.gbl...

Almost but not really. You talkin about clients sending requests or a
server that listens for incomming socket connections?
--
wjs mvp

"Jacob" <[e-mail]> wrote in message
news:6ndRc.4869$Lj.426@fed1read03...

Is there any tutorials or documentation that you could point me towards
regarding pooling requests for a limited number of sockets?

I want users of this class to be able to request a socket and if one isn't available, their request will be queued and a socket returned when it is
available. Consequently, if a socket is no longer in use, how to return it to the pool. This is all in an attempt to not make so many connections

to a

particular port, but use one if it has already been established.

Does anybody know what I'm talking about?

Any help is appreciated.

Thanks,
Jacob

[Mark Rees]

Jacob,

Check out this article
http://www.devarticles.com/c/a/C-Sha...asses--Part-I/

Mark

On Sun, 8 Aug 2004 00:55:00 -0700, "Jacob" <[e-mail]> wrote:

Clients sending requests....

Just looking for a really smart way to manage the requests/sockets. (If the
analogy helps, think of it like a SQL connection pool, but for sockets).

Thanks,
Jacob

"William Stacey [MVP]" <st*****@mvps.org> wrote in message
news:%2***************@TK2MSFTNGP12.phx.gbl...

Almost but not really. You talkin about clients sending requests or a
server that listens for incomming socket connections?
--
wjs mvp

"Jacob" <[e-mail]> wrote in message
news:6ndRc.4869$Lj.426@fed1read03...

> Is there any tutorials or documentation that you could point me towards
> regarding pooling requests for a limited number of sockets?
>
> I want users of this class to be able to request a socket and if oneisn't > available, their request will be queued and a socket returned when it is
> available. Consequently, if a socket is no longer in use, how to returnit > to the pool. This is all in an attempt to not make so many connections

to

a

> particular port, but use one if it has already been established.
>
> Does anybody know what I'm talking about?
>
> Any help is appreciated.
>
> Thanks,
> Jacob
>
>

[Jacob]

Thanks for the link... a good refresher on .Net sockets, but nothing new,...
or more importantly, nothing to help me in the direction I'm going. Perhaps
I'm not explaining it well. Let me put it in an example.

Say I'm connecting to an HTTP server on port 80. The server allows me a
maximum of two connections, but I have a rich client that could want to
interrupt any of the current connections, use them, and then return them to
what they were doing already. The easy way would be to terminate connections
and connect on each request, but I'm trying to improve efficiency by
creating a socket abstraction layer so that when I pass a connection to
something else, it will think that a connection was just made when in
reality, it's an already established connection. And consequently, when
whatever is using that connection calls Close, it will actually just go back
to the pool.

Any help would be appreciated.

Thanks,
Jacob
"Mark Rees" <ma*******@paradise.net> wrote in message
news:8i********************************@4ax.com...

Jacob,

Check out this article
http://www.devarticles.com/c/a/C-Sha...asses--Part-I/
Mark

On Sun, 8 Aug 2004 00:55:00 -0700, "Jacob" <[e-mail]> wrote:

Clients sending requests....

Just looking for a really smart way to manage the requests/sockets. (If theanalogy helps, think of it like a SQL connection pool, but for sockets).

Thanks,
Jacob

"William Stacey [MVP]" <st*****@mvps.org> wrote in message
news:%2***************@TK2MSFTNGP12.phx.gbl...

Almost but not really. You talkin about clients sending requests or a
server that listens for incomming socket connections?
--
wjs mvp

"Jacob" <[e-mail]> wrote in message
news:6ndRc.4869$Lj.426@fed1read03...
> Is there any tutorials or documentation that you could point me towards > regarding pooling requests for a limited number of sockets?
>
> I want users of this class to be able to request a socket and if one

isn't

> available, their request will be queued and a socket returned when it is > available. Consequently, if a socket is no longer in use, how to

returnit

> to the pool. This is all in an attempt to not make so many

connectionsto

a
> particular port, but use one if it has already been established.
>
> Does anybody know what I'm talking about?
>
> Any help is appreciated.
>
> Thanks,
> Jacob
>
>

[Jacob]

What I'm looking for is actually someting like this, but for a socket
connection:

http://msdn.microsoft.com/library/de...taprovider.asp
Thanks,
Jacob

"Glenn Wilson" <ir****@hotemail.com> wrote in message
news:uG****************@TK2MSFTNGP11.phx.gbl...

I would have a look at threading to control the sockets.
Get the users to use a UDP Port to request a Connection, when this
connection is successful send back a UDP Message withthe connection detail
for a TCP Port to connect to (Also Send a Hash value say the IP Address and port as well as some secret Code, to be used to verify that the incomming
connection is allowed to connect at this time)
"Jacob" <[e-mail]> wrote in message
news:6ndRc.4869$Lj.426@fed1read03...

Is there any tutorials or documentation that you could point me towards
regarding pooling requests for a limited number of sockets?

I want users of this class to be able to request a socket and if one isn't available, their request will be queued and a socket returned when it is
available. Consequently, if a socket is no longer in use, how to return it to the pool. This is all in an attempt to not make so many connections

to a

particular port, but use one if it has already been established.

Does anybody know what I'm talking about?

Any help is appreciated.

Thanks,
Jacob

[William Stacey [MVP]]

Have two initial swags at this (if I understand your requirements)
1) Create a pool object. This object will contain two (or more) connection
objects that abstract a socket and they will keep their socket open. Use a
semaphore with a count of 2 to protect the number of owning connection
objects that can be out at any one time. More requests will just block
until someone that owns a connection object closes it. When closed, the
connection object will release 1 semaphore to add it back to the pool.

2) Abstract connection at a higher level. Have one connection object and a
C-queue that client object can put requests into. The connection object
then just services the queue and you figure out who to send reply back to -
maybe another reply queue for each client.

--
William Stacey, MVP

"Jacob" <[e-mail]> wrote in message
news:w3BRc.5961$Lj.440@fed1read03...

Thanks for the link... a good refresher on .Net sockets, but nothing new,... or more importantly, nothing to help me in the direction I'm going. Perhaps I'm not explaining it well. Let me put it in an example.

Say I'm connecting to an HTTP server on port 80. The server allows me a
maximum of two connections, but I have a rich client that could want to
interrupt any of the current connections, use them, and then return them to what they were doing already. The easy way would be to terminate connections and connect on each request, but I'm trying to improve efficiency by
creating a socket abstraction layer so that when I pass a connection to
something else, it will think that a connection was just made when in
reality, it's an already established connection. And consequently, when
whatever is using that connection calls Close, it will actually just go back to the pool.

Any help would be appreciated.

Thanks,
Jacob
"Mark Rees" <ma*******@paradise.net> wrote in message
news:8i********************************@4ax.com...

Jacob,

Check out this article

http://www.devarticles.com/c/a/C-Sha...asses--Part-I/

Mark

On Sun, 8 Aug 2004 00:55:00 -0700, "Jacob" <[e-mail]> wrote:

Clients sending requests....

Just looking for a really smart way to manage the requests/sockets. (If the

analogy helps, think of it like a SQL connection pool, but for

sockets).
Thanks,
Jacob

"William Stacey [MVP]" <st*****@mvps.org> wrote in message
news:%2***************@TK2MSFTNGP12.phx.gbl...
> Almost but not really. You talkin about clients sending requests or a> server that listens for incomming socket connections?
> --
> wjs mvp
>
> "Jacob" <[e-mail]> wrote in message
> news:6ndRc.4869$Lj.426@fed1read03...
> > Is there any tutorials or documentation that you could point me

towards> > regarding pooling requests for a limited number of sockets?
> >
> > I want users of this class to be able to request a socket and if oneisn't
> > available, their request will be queued and a socket returned when

it is> > available. Consequently, if a socket is no longer in use, how to returnit
> > to the pool. This is all in an attempt to not make so many connectionsto
> a
> > particular port, but use one if it has already been established.
> >
> > Does anybody know what I'm talking about?
> >
> > Any help is appreciated.
> >
> > Thanks,
> > Jacob
> >
> >
>
>