client/server design pattern

Hi all,

In Client/Server application, clients might be there in private network
and server will be there in public. End user can connect to server from more
than one machine (so, more than one client). Now, I need to update user
information in client machine. i mean, we need to maintain some information
of user in both ends client and server. To achieve this any design patterns
are there?

Thanks in advance.



.

Relevant Pages

  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)
  • Re: XP join SBS 2003
    ... I've created both the users and client machine via Add User Wizard. ... Everything else on the server seems to be functioning perfect, ... I also didn't modify the server network card. ...
    (microsoft.public.windows.server.sbs)
  • [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
    ... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
    (Full-Disclosure)
  • Re: What doesnt lend itself to OO?
    ... > rather than client code. ... no way to do that without also touching the object with clock semantics ... will not encapsulate both clock semantics and network semantics. ... The server can do whatever it wants ...
    (comp.object)