Re: Re: XML socket server HTTP tunneling

Sorry, I did phrase my question too well.

To answer Merlyn, I am not opening an XML socket, I am opening a standard socket and using this to send and recieve XML data.

In response to mirod, I cant get the network admins to open ports because this is going to be a public service that anyone can connect to, I dont have a problem connecting but other people behind firewalls might have a problem doing this.

I think the solution might be to use port 80 to connect to a cgi which send xml data and loads data, then closes the connection. The client then waits for a bit, reconnects and does the same again. I will then have to modify the server code so that it stores all of the messages sent since the last time the user connected and sends them in one go when the user connects. This wouldnt be a real time message relay so i dont think it would be any good for games.

Is this the best solution?

Comment on Re: Re: XML socket server HTTP tunneling

Replies are listed 'Best First'.
•Re: Re: Re: XML socket server HTTP tunneling by merlyn (Sage) on Nov 21, 2002 at 13:31 UTC
That's what SOAP is! Stop trying to reinvent things. -- Randal L. Schwartz, Perl hacker Be sure to read my standard disclaimer if this is a reply.	[reply]
Re: •Re: Re: Re: XML socket server HTTP tunneling by JamieD (Novice) on Nov 21, 2002 at 17:00 UTC
I dont want to use SOAP becuase it adds a whole shed load of code that A)I dont want and B)dont need. This will use up extra resources that I dont want to. Why do I need to use serveral pm's when I can do the same thing in a few lines of code? The whole point of my server is to be as fast and stable as possible while also being easy to port to other platforms. For these reasons I only want to use pm's if absolutly nessacery	[reply]