> > It may be possible but only by having objects in one thread hold > pointers to data owned but another thread (in another interpreter). > That's not good. >
My idea (in the long term) is to have the data of the inner handle stored in a shared area and the outer handler still per thread. So every thread that uses a handle has a copy of the outer handle that point's to the shared inner handle. All DBI data, except the outer handle, would always be created in this shared area. Maybe I am missing something, but I think something along these lines should work. Of course this is the long term perspective, because my time is limited, as yours is... > For the short term (and possibly medium term) I think we need to > be more restrictive than that. If only for our own sanity. > ok, agreed > > The ability to share handles, is one of the reason to use > > threads, isn't it? > > It would certainly be nice - but very hard to get right and safe. > yes > > But I'd still urge you to get the rest of the groundwork in place asap ok, I try to do this during the next days. I see how far I will get... > (ideally before the perl conference in a couple of weeks time - then I > can put your name up in lights :) > That's not the reason why I do this, also it's nice to hear my name at such places :-) I will also be there and if necessary we can talk there about further details. Gerald ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 -------------------------------------------------------------
