| re: multiplayer: possible with http?
Bear in mind the one problem you're going to be having is real-time data
over HTTP. Because HTTP is a request-response protocol by default, your
client will be required to continually request data from the server -
the server won't be able to PUSH data to the client.
This may or may not be an issue for you. I just now that a few years
back when I worked on a real-time stock market trading system, the lag
for users on dial-up made the system very slow, and ultimately useless
in a real-time context.
dondiego wrote:
[color=blue]
> Hello Everybody
>
> Im going to develop a multiplayer game. I will use a servlet and an applet
> on the client side. I see two possible ways to mantain the contact between
> the clients and the server:
>
> By an http connection
> By a not-http connection, eg sockets
>
> I think that the big disadvantage in using a connection that relies on http
> is that the application, on both sides but principally on the sever, becomes
> very complex. However the advantage with this approach is that you dont need
> to have your own server to set up the multiplayer platform.
>
> It would be much easier to program a server that is a standalone java
> aplication listening on some port, or a servlet even this listening on a
> port. But here the problem is that you need total access to the server,
> which is much more expensive.
>
> Does anyone have any suggestion about this problem? If there is another way,
> maybe? Or if its actually too complex to develop a multiplayer without
> docket programming? Or maybe that the http approach isnt so bad? Thanks in
> advance.
>
> Paolo
>
>[/color]
| 
