jQuery in Action, 2nd edition*
The moose likes Distributed Java and the fly likes Socket programming by TCP/IP - advantages/disadvatages Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » Distributed Java
Bookmark "Socket programming by TCP/IP - advantages/disadvatages" Watch "Socket programming by TCP/IP - advantages/disadvatages" New topic
Author

Socket programming by TCP/IP - advantages/disadvatages

dhanya kairali
Greenhorn

Joined: Dec 28, 2000
Posts: 22
A non java client needs to invoke my java application.
Suppose the Java application doesnt do much in terms of data sent to and fro between the client and the server.
I want my application to have 1. high performance and 2. low response time.
I also expect a 3. huge volume of transactions.
What are the pitfalls there might be if I decide to go ahead with implementing my Java Application as a Multi threaded server program ?
What are the choices I have . Am I mistaken in thinking that if I go ahead with a solution like using a Webservice it will have performance issues when compared to my simple solution? My simple solution in fact aims to solve a simple problem eg - maybe query a database to return a true or false to the client.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Socket programming by TCP/IP - advantages/disadvatages
 
Similar Threads
upload and download file to any machine in a n/w
How did you go about server reading data filу when started from jar?
Using RMI vs Socket programming
Passed Part II and III
Available space for file on server