🚀 go-pugleaf

The server is a form of proxy. Itll recieve a request on one socket, and the
server opens a socket to another server, pass the request, recieves the
response and forwards back to the client over the socket the client
origionally openned (which of course must not close).

Here's how it goes: Client connects to server. OnRead, server enqueues a new
thread (using our own TSuperThreader). When the time comes for the thread to
execute, the thread then parses the request, establishes a connection to the
appropriate server, asks for the data and waits. It will wait until a
response comes back or times out. Once either happen, the recieved data is
then forwarded to the client.

Trouble is that we don't know when the *server* must close the connection -
we are relying on a timout or the client terminating the connection - which
is dodgy.

Any ideas, anyone?

Tharun


"Hans Galema" <j.m.galema.dontusethis@maartens.nl> wrote in message
news:3edccfa2$1@newsgroups.borland.com...
> Tharun Pillay wrote:
> > Hans, I cannot close the socket when SendBuf returns because it is a
> > non-blocking server.
>
> What is the reason ?
>
> What happens if you add a
>
> TServerSocket1->Socket->Connections[connectionnr]->Close();
> or a
> TServerSocket1->Socket->Close();
> or a
> TServerSocket1->Close();
>
> or a combination of these, right after ...->SendBuf () ?
>
> Hans.
>