Re: Distributed Objects between cats
Re: Distributed Objects between cats
- Subject: Re: Distributed Objects between cats
- From: Aurélien Hugelé <email@hidden>
- Date: Fri, 12 Aug 2005 10:43:30 +0200
On 11 août 05, at 23:38, Greg Parker wrote:
email@hidden wrote:
I tried /usr/bin/g++-3.3 on Tiger and it generates (in the
__cat_inst_meth section) ...4nO... whereas gcc4.0 produces ...4On...
Now: Is this a feature or a bug?
It's a bug. Look for the fix in the next developer tools update.
thnaks to confirm my intuition ! please release it soon. We are
currently having problems with customers that want compatibilities
with old and new versions of our product !
email@hidden wrote:
Unfortunately DO is effectively dead - Apple don't support it, nor
have any interest in continuing it's existence. The odds of this
being "fixed" (i.e. worked around) are about nil to none.
Distributed Objects is quite alive. It's not being aggressively
pushed forward, but neither has it been deprecated or left to die.
--
Greg Parker email@hidden Runtime Wrangler
DO is, imo, a jewel because it offers incredible possibilities. It's
very easy to implement. Fast, and very convenient.
But as Wade said, it is not well documented (it took me for example
several days to understand why bycopy did not work as expected, only
*old* WO lists explain that you should implement - (id)
replacementObjectForPortCoder:(NSPortCoder *)encoder to override
NSObject default implementation).
DO implementation is *very* obscure and i have many problems myself
to use them in complex system (not just a simple client/server design
but more like PeerToPeer design where any peer can message any other
peer, and everything in a robust manner).
Almost no example is given. The only example from Chris Kane is on
the lists, not even on Apple Developer site !
DO are often "blocking" because the server is not responsive (due to
message in a wrong thread, a dead client, a long transfer etc...)
Do are extremly complex to use in a multithreaded environement, to me
that is the major problem.
etc...
I dont think it is deprecated or left to die, but they clearly need a
little more attention and refresh ;-)
_______________________________________________
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