Start with a simple version and add features when you get it working.
NormR1
Posting Expert
6,677 posts since Jun 2010
Reputation Points: 1,138
Solved Threads: 656
The client and server will probably be quite different programs, with completely different installation requirements, so I would say "keep them separate". The client will probably just be a single jar file, but the server will be a different jar, plus database etc.
Either way, your installer can still ask the user which to install and do whatever is required. There's no reason why the installer and the application(s) should have the same structure.
JamesCherrill
Posting Genius
6,371 posts since Apr 2008
Reputation Points: 2,130
Solved Threads: 1,073
Be careful about Jaydenn's input. People write client server in Java all the time without ever needing to touch binary or bitwise operations, or feeling any need to use software outside the standard Java SE API.
Don't take my word for this, read the official tutorial - just four pages starting at
http://download.oracle.com/javase/tutorial/networking/sockets/index.html
JamesCherrill
Posting Genius
6,371 posts since Apr 2008
Reputation Points: 2,130
Solved Threads: 1,073
@rsnitch:
This thread is long dead.
If you have a proposal for a good way to do client/server in Java please start your own topic
JamesCherrill
Posting Genius
6,371 posts since Apr 2008
Reputation Points: 2,130
Solved Threads: 1,073
In a Java forum you will need to explain why it is better than simply using the existing tried and tested Sockets and ObjectOutput/ObjectInput streams in the standard Java API.
JamesCherrill
Posting Genius
6,371 posts since Apr 2008
Reputation Points: 2,130
Solved Threads: 1,073