> I am trying to implement a consumer-producer scenario communicating
> via HTTP pipelining.
[quoted text clipped - 24 lines]
> problems please help me.
> thank you in advance
You have a server that runs on predefined port (this is a must -
otherwise you have no way of starting the conversation). When your
server receives first request (see handshake) it should open NEW
connection over some available port (this is not the same predefined
port you send you initial request to). If you try to look at tcp-ip
conversation between your browser and any web server you can see what
happens. Then any further message exchange happens over this new pair
(one on server, one on client) of ports until you close your
connection. You can find a lot more info and examples if you search
google for 'java socket programming'.
stavrinio@gmail.com - 17 Aug 2007 21:13 GMT
> > I am trying to implement a consumer-producer scenario communicating
> > via HTTP pipelining.
[quoted text clipped - 35 lines]
> connection. You can find a lot more info and examples if you search
> google for 'java socket programming'.
Question to all that you said how can I succesfully implement
pipelining from what you wrote before I am not sure if
it will work at all if i try to open many sockets and send single
message from different socket that is not pipelining at
least of what i know:)