At 09:20 PM 8/3/2002 -0700, Brad LaFountain wrote: >This isn't always ideal. I would rather see the threads as a function not a >separate file. Forcing threads to a file would be pretty limited.
I don't think it's that limited. I also don't think that duping the whole thread's address space is a good idea. It's slow and prone to errors. Andi > -brad >--- Andi Gutmans <[EMAIL PROTECTED]> wrote: > > I still think that if you're going to implement such a thread extension it > > shouldn't try and copy it's parents data-structures. It'd be very slow and > > prone to errors. > > I think giving a filename as the starting point of the thread would be the > > best solution. It'd mean that the thread is pretty much a completely new > > request. It would also mean much leaner threads as you could create .php > > files with only the logic the thread requires. > > > > Andi > > > > At 02:30 PM 8/3/2002 -0700, Shane Caraveo wrote: > > >I've cleaned things up a bit, removed code from tsrm and added it to a > new > > >file, and commited to pecl. This way those interested can start playing > > >with and developing the module. > > > > > >Shane > > > > > > > > >-- > > >PHP Development Mailing List <http://www.php.net/> > > >To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > -- > > PHP Development Mailing List <http://www.php.net/> > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > >__________________________________________________ >Do You Yahoo!? >Yahoo! Health - Feel better, live better >http://health.yahoo.com -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
