Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Client-server

 
vishal sodani
Ranch Hand
Posts: 127
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I am going to develop a client(in Swing)-server application.What technology should I use-J2EE,or simply RMI.Or some other tech
thanks
 
inam paki
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
RMI is better solution if u don't 've any concurrency issue n transaction issue in ur application involved.
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by inam paki:
RMI is better solution if u don't 've any concurrency issue n transaction issue in ur application involved.

Now hold on there, partner. What about scaleability? That's a distinguishing feature between EJB servers and RMI servers, too.
Kyle
 
Garandi Garandi
Ranch Hand
Posts: 192
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am agree with Kyle Brown about scaleability issue.
Garandi
 
vishal sodani
Ranch Hand
Posts: 127
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here is the link where i have discussed my problem
http://www.coderanch.com/t/335298/GUI/java/Swing-vs-VB
thanks
 
vishal sodani
Ranch Hand
Posts: 127
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Any suggestions
 
Sudd Ghosh
Ranch Hand
Posts: 187
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Vishal-
I went thru the link. Your "chip factory" GUI doesn't look so overwhelming. Why don't you stay with only J2EE, with HTML/DHTML/JSP as the front-end view, and EJB for the business methods ? I have worked with Swing and I know it can result in pretty GUIs, but I am not at all sure how to interact a Swing client with the EJB backend.
Someone said that one has to use RMI. Will it be then that the Swing client, ALSO acting as a RMI stub, has to call the RMI skeleton/server method which, in turn, will act as a client to the EJBs? I want to know more about this.
Also I was reading somewhere that Swing should be avoided with the app server beans code (to avoid implicit multithreading), but then may be it is ok on the client side. I have personally found Swing to be very slow on Solaris (I had a large menu/submenu hierarchy, it was with Java 1.3).
Thanks, Sudd
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic