>> Sure, extending WO so that EOF become multi-threaded or anything like this >> would be a huge task, but from my point of view (a non-technical one), we >> can do a lot on top of WO to "fix" problems. And to me, it make more sense >> to extend WO than trying to rewrite it... > Depending on how you understand "multithreaded", that's already implemented > or in fact pretty easy to do. Andrus (I think?) has done some work on that > years ago. I think I would define multithreading to be something like multiple EOF stacks that don't blow out memory ... Ultimately that requires some form of lockless snapshot cache. We get the first half with object store coordinator pools, but not the second part.
ms _______________________________________________ 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]
