fully implement client / server disconnect

[progether]

fully implement client / server disconnect

[projectdelphai]

I'm not sure if sockets in java are cross-platform and cross-language. Is it actually possible to have jadventure create a socket and have a python script connect to it? Or do we need to use something other than a socket such as a unix pipe or a serial port or a local webserver. I'm not really sure.

[CageHN]

Sockets are tcp/ip standard. As long as we define clearly the JAdventure
protocol (including encoding we want to use) anyone could implement a
client.
On Sep 20, 2014 7:58 PM, "Reuben Castelino" [email protected]
wrote:

I'm not sure if sockets in java are cross-platform and cross-language. Is
it actually possible to have jadventure create a socket and have a python
script connect to it? Or do we need to use something other than a socket
such as a unix pipe or a serial port or a local webserver. I'm not really
sure.

—
Reply to this email directly or view it on GitHub
#89 (comment).

[verhagen]

Would it be an idea to make it available through a RESTful API? Which is also an easy standard for other to understand and to implement by any language.

[CageHN]

Web services Rest/SOAP are not ideal for something that is so user interactive. Using sockets, if we didn't have a JAdventure client, we can even connect to the game using any standard telnet client.

[projectdelphai]

bulk is already done, #90 needs to be fixed, some more clients should probably be created and http remote testing needs to be tested.

[paddatrapper]

I've tested the HTTP remote and works the same as local network with the only difference being the changed hostname in Client.java. My testing shows that there are no bugs in running the game over the internet between two completely separate computers.

[projectdelphai]

Wait really? That's awesome! For alpha testing for sure at least, knowing that it works at a basic level is all we really need. Alpha testers can then beta test it and see if it works for more stressful testing. I'll close this issue then since that's all that we really needed to test for this. Last thing we need is just some semi-reliable clients and then we're good.

[paddatrapper]

Also need to change the hostname setting to be independent of the code so that it can be changed without recompiling the jar file

[projectdelphai]

Oh, right. Okay, I'll create an issue for that. It should probably just be another argument that is used when using server/client. So the default client/server will take in another argument that is the hostname and desired port.