exactly. the knock-on problems you mentioned are well solved and well documented. realtime programmers using threads have to get their heads around it on their first realtime project.
i don't like doing my code in c(++), or worse; having to interface between c(++) and php. i chose php because my code can stay close to simple english that way. what you're suggesting is highly intrusive in my work-style, one that you're not affected by at all. in fact if you make things more difficult for me, i have less time to release opensource code of my own. On Wed, Mar 24, 2010 at 10:59 AM, Per Jessen <p...@computer.org> wrote: > Tommy Pham wrote: > >> When you do use AJAX, there is a slight difference in your app design >> then when you don't use AJAX. That's the way I see threads. > > A threaded design makes for a lot more than a slight difference IMHO. > Once you've said "threading", the next words in rapid succession are: > mutexes, semaphores, locking, spin-locks, signals, race conditions, > atomic updates, cache coherency, asynchronous IO etcetera. They are > all perfectly well-known but complex concepts, and I would always > choose C and/or assembler to work with those. > > > > -- > Per Jessen, Zürich (9.5°C) > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
