help: RMI or JNLP

were currently building an enterprise software built in J2SE

i would just like to ask which is a better option

1) Create a Client-Server Application that uses JAVA RMI

- The Client will have the Application Display and will be passing

data/information to the Server

- The Server will consist of the SQL's and process the information

needed by the clients and pass the data through RMI

2)Create a JAVA Application (jar file) and make it acessible to the client via a JNLP file

-The application will have both the design/form as well as the SQL's

which will be better to use among the two options in terms of data processing/transfer speed and server process load? the application will run on a local network

hope someone can help us decide

thanks in advance

(* we are not using any JAVA server, we just installed a J2SE sdk in the server)

Message was edited by:

darkoasis09

[965 byte] By [darkoasis09a] at [2007-11-27 4:30:10]
# 1
RMI is a better choice if you want to distribute your application. Data processing is and rate of transfer are completely depends on the design of your application. Load balancing can be done i guess. I have no idea about JNLP.
AnanSmritia at 2007-7-12 9:39:22 > top of Java-index,Java Essentials,New To Java...
# 2
What do you consider to be an SQL? Why is RMI needed to make database calls? Sounds like you have some very fuzzy requirements, and some very fuzzy definitions, too. A recipe for a failed project! I've never heard of RIM and JNLP being two alternatives to solve the same problem
georgemca at 2007-7-12 9:39:22 > top of Java-index,Java Essentials,New To Java...
# 3

> RMI is a better choice if you want to distribute your

> application. Data processing is and rate of transfer

> are completely depends on the design of your

> application. Load balancing can be done i guess.

> I have no idea about JNLP.

You have no idea about JNLP, so RMI must be the better solution?

Herko_ter_Horsta at 2007-7-12 9:39:22 > top of Java-index,Java Essentials,New To Java...
# 4

I think you need to read up on Web Start-JNLP.

You can start your client using Web Start and have it talk to the server using RMI.

Web Start is not a communication protocol, RMI is.

Web Start is a method for launching applications on machine by downloading the configuration and jars from another machine. Grossly oversimplifying here.

RMI is a method by which two processes communicate with each other.

BenHill70a at 2007-7-12 9:39:22 > top of Java-index,Java Essentials,New To Java...
# 5

> > RMI is a better choice if you want to distribute

> your

> > application. Data processing is and rate of

> transfer

> > are completely depends on the design of your

> > application. Load balancing can be done i guess.

> > I have no idea about JNLP.

>

> You have no idea about JNLP, so RMI must be the

> better solution?

I did not mean that RMI must be the better solution. I have written RMI is a better choice when you want to distribute your application.

read my post again

AnanSmritia at 2007-7-12 9:39:22 > top of Java-index,Java Essentials,New To Java...
# 6

> > You have no idea about JNLP, so RMI must be the

> > better solution?

>

> I did not mean that RMI must be the better solution.

You said it but you didn't mean it?

> I have written RMI is a better choice when you want

> to distribute your application.

'Better choice' than what? than JNLP about which you have no idea? than something else? what?

Can we try to keep it logical please.

ejpa at 2007-7-12 9:39:22 > top of Java-index,Java Essentials,New To Java...