RMI and concurency

Hi!

I am developing a client/server project in Java (client/server - THE tundra for Java) and I (of course) use RMI. My quesion is: is RMI inherantjy multi-user or do I need to go the extra mile to allow multi use.

The set-up is as follows: ther is one server with a database. Clinets can access the database invocint methods on the Interface. Everything works fine (well, not everything yet - it IS still a work in progress) ... for one user: me: the developer. The main (one of) concern is: what is I let this thing "loose in the wild"? Will it be able to handle multiple connects? And what about connection pooling? I have a Connection Class set up on the server, and it gets passed around nicely, ib the instance of the server ... for me.

Thanks for your reply!

T01dev

[803 byte] By [T01deva] at [2007-11-27 10:29:32]
# 1

> is RMI inherently multi-user

It is inherently multi-threaded

> or do I need to go the extra mile to allow multi user.

You need to ensure your code is appropriately synchronized where necessary to execute multi-threaded.

If that's what you're really asking.

> Will it be able to handle multiple connects?

Yes.

> And what about connection pooling?

RMI does that.

ejpa at 2007-7-28 17:58:00 > top of Java-index,Core,Core APIs...
# 2

Thank you!

Now I know I am on the right track - as if I coukld be wring using Java ... ,-)

T01deva at 2007-7-28 17:58:00 > top of Java-index,Core,Core APIs...