Is the Remote Object always a singleton?

Question

Hi,
Using .Net Remoting we can export a Remote Objects in three different ways:
1. Singleton: Same instance of a Server-side object is used by all the clients for all the requests.
2. SingleCall: Whenever a new call is received, a new instance of the Server-side object is created and reference is passed to the client. Therefore, for each call to the server, the client gets a new instance of the object.
3. Client Activation: In this, the Client requests to the server for creating a new instance which can be used for multiple calls. The instance activated by a client is not used by other clients. Client-Activated objects can store state information between method calls for its specific client.
Do we have this options in RMI or the Remote Object must always be a Singleton?
What I'm looking for is a way to create one instance of the Remote Object (in the server side) to each client that connects to a server.
thx

Answer 1

Do we have this options in RMI1 and 3 are available. 2 is not.
or the Remote Object must always be a Singleton?No.
What I'm looking for is a way to create one instance of the Remote Object (in the server side) to each client that connects to a server.It's as simple as 'return new MyRemoteObject(...);'.
For example:
public interface Login extends Remote
  public Session login(String username, ...) throws RemoteException;
public interface Session extends Remote
  // your client API here
public class LoginImpl extends UnicastRemoteObject implements Login
  public Session login(String username, ...) throws RemoteException
    // validate username etc. If OK return a session.
    return new SessionImpl();
public class SessionImpl extends UnicastRemoteObject implements Session
  // your client API implementation here, also all the server-side state belonging to that client session
}Note that this is as secure as the login() method. By type safety, nobody can execute Session methods until they have logged in.
I'm deleting your two other threads.