Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Yet another threading question...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Yet another threading question...

Subject: Yet another threading question...
From: Stamenkovic Florijan <email@hidden>
Date: Thu, 26 Feb 2009 17:01:29 -0400

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@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden Follow-Ups: Re: Yet another threading question... From: Chuck Hill <email@hidden> Prev by Date: Re: WebObjects Installer CD for Windows Next by Date: Re: Java 1.6 via SoyLatte on MacOS X 10.4.11 Previous by thread: Re: question on security scanning Next by thread: Re: Yet another threading question... Index(es): Date Thread