Client/Server guidance
Client/Server guidance
- Subject: Client/Server guidance
- From: Terry Smyth <email@hidden>
- Date: Tue, 15 Oct 2002 10:50:05 +0100
Dear list,
From a relative newcomer to Cocoa...
I'm writing a Cocoa application which will normally run in a server
environment (it's mostly a configuration front end to configure data
required by another server process). I'd like to allow the user to run
my app from his desktop Mac, rather from some noisy server room. I'm
wondering what is the easiest way to achieve this separation of UI from
underlying functionality.
My research is pointing me towards a client/server architecture, built
around Distributed Objects, where a vended server object controls the
data, and passes it to the clients for display and update. Does this
sound like the right approach? Is there an easier way achieve what I
want. (I recall that under Motif/X11, you can just set the DISPLAY
variable to any other machine, then launch the app on the server, but
with a remote UI. I don't suppose there is anything like this under
Cocoa??)
Assuming DO is the way forward, I have a couple of further questions.
I'd love to get my hands on some sample code, but could not find any in
the usual places. Does anyone know where I could find some?
Also, what is the recommended way to deal with
Authorization/Authentication in a DO context. I'm familiar with the
AuthTool sample, whereby the authorization API prompts the user for a
password if required. What happens if the server part of my app
requires some authorization (which would need to be entered at the
client side)? Is there a mechanism to deal with this?
Thanks for any advice or pointers,
Terry Smyth
Software Generation Limited
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.