• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
  • paul wheaton
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Henry Wong
Saloon Keepers:
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Tim Moores
  • Mikalai Zaikin
Bartenders:
  • Frits Walraven

Socket programming by TCP/IP - advantages/disadvatages

 
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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.
 
There's a way to do it better - find it. -Edison. A better tiny ad:
Gift giving made easy with the permaculture playing cards
https://coderanch.com/t/777758/Gift-giving-easy-permaculture-playing
reply
    Bookmark Topic Watch Topic
  • New Topic