Re: Distributed objects: Code required on both sides?
Re: Distributed objects: Code required on both sides?
- Subject: Re: Distributed objects: Code required on both sides?
- From: James Bucanek <email@hidden>
- Date: Sun, 30 Apr 2006 08:59:35 -0700
Philippe Mougin wrote on Sunday, April 30, 2006:
>Chris Hanson wrote:
>
> >On Apr 29, 2006, at 11:09 AM, James Bucanek wrote:
> >
> >> I now have a lot (and it's growing every day) of classes
> >> that only execute in the server. These objects never exist
> >> in my application except as proxy objects. I'd like to
> >> eliminate that code in my application so that the code
> >> only exists in the server.
> >> Is this possible?
> >
> > Yes. The way to do it is to define a protocol to represent
> > the server-side object (which the server-side object should
> > of course conform to) and to write your client-side code in
> > terms of the protocol, e.g. "id<ServerSideObjectProtocol> foo;"
> > rather than "ServerSideObject *foo;". This way your client-side
> > code only references the protocol, and doesn't need
> > implementations for the server-side objects.
>
>Yes, and even using a protocol is optional. You can have a completely
>dynamic client if you want.
Thanks for the confirmation. Someone wrote me off-list and explained what my real problem is.
I have some factory methods that call class methods (+[RemoteCommand commandWith...]). These, naturally, reference the object's class object and create a linker reference that has to be resolved. If I remove these from my application, I should be able to remove all vestiges of the server code in my client.
--
James Bucanek
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden