Re: Exchanging information

On Fri, 27 Jul 2007 22:42:16 -0700, Mark Space wrote:

Haggis McMutton wrote:
I'm writing a distributed application which includes one server and many
clients that will be exchanging data.

I've made my own crude protocol that uses sockets and simply puts data on
single lines separated by new line characters.

I want to extend this to something a bit more advanced. I was thinking of
using XML but someone said I should use SOAP, but that uses HTTP which
seems to complicate things. Any ideas on the best way to do this?

Serializing objects over a socket should work much the same as sending
lines with a newline at the end. Might be the easiest solution being
the closest to a drop in replacement.

I should mention that I'm very likely to want to write the client in a
different language in the future so I need a way of doing it that can
easily be done in other languages. I can't be Java specific.

Query: why change it if it's working now?

Because I want to expand on it, and I think it would be a lot more work
and more prone to error if I carry on writing my own protocol.
.

Relevant Pages

  • Exchanging information
    ... clients that will be exchanging data. ... I've made my own crude protocol that uses sockets and simply puts data on ...
    (comp.lang.java.help)
  • sockets, closing and TIME_WAIT
    ... During heavy load the server can't follow anymore because the sockets ... my server should be able to handle 10 clients connecting ... This gets a free position in the array of connections, ...
    (comp.unix.programmer)
  • Re: blocking non blocking
    ... not connected to incoming data on the same thread, async sockets have to be ... somehow a server with 50K threads, ... or overlapped I/O servicing 50K clients. ... read and learnt about blocking and non blocking, ...
    (microsoft.public.win32.programmer.networks)
  • Re: validating client in socket communciation
    ... sockets kept open through out or shall the client open the connection ... performance-wise there is even more overhead opening and closing connections between the server and the same client over and over. ... Unless clients only communicate with the server very infrequently, you should just keep their connections open. ... a server supporting 1 million sockets is going to have to get _everything_ right. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Moving files from clients to the server
    ... I'm not very familiar with sockets but I'll look into that, ... >> files should be passed to the server. ... the fastest way to create them is on the clients' machines. ... >> Another solution is to steam the files over the network. ...
    (microsoft.public.vc.atl)