Hi all,
I thought of making an EOEditingContext subclass that encapsulates a
thread and it does all it's work on that single thread, regardless of
which thread a method call to it is made on. It would entail
overriding all the methods in the EOEditingContext to do something
like a producer / consumer setup. I think that if well made, it would
introduce minimal overhead, as any inactive thread would be waiting,
and would insulate the EOEditingContext from the multithreading
outside of it. I have not thought it through very well (though I am
pretty sure it can be made), so, can anyone think of unexpected bad
side-effects?
Also, this is happening on the client side, though I am not sure if
that makes much of a difference for this.
Thx,
F
- still trying :) I was just about to ditch all the multithreading in
my client app, saw how much it'd slow it down and make it less user
friendly, and I just can't do it without another shot at it...
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
