This week's book giveaway is in the Artificial Intelligence forum.
We're giving away four copies of Pragmatic AI and have Noah Gift on-line!
See this thread for details.
Win a copy of Pragmatic AI this week in the Artificial Intelligence forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

Socket programming by TCP/IP - advantages/disadvatages  RSS feed

 
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!