> Could you share some more infos about that project?
sure
the project itself is my university thesis, its topic might clear some
things: 'Hive -distributed server for message-driven componental PHP
applications'. main idea is to be able to create php applications in
RAD-way. for this to be possible i designed componental architecture based
on messaging system. it is exacly the way php is NOT designed to be used ;)
all this with transparent component distribution in mind. server runs as
standalone appliacation. http daemon uses sockets to transfer request
parameters and fetch results - later i`ll probably build into app server
simple httpd. server is ('will be' mostly) coded in php, so changes can be
made easily, but if my idea will be useful i have in mind rewriting code in
c. no stress tests have been made so far - to much coding is still to be
done.
it is mix of ideas from java, windows messaging and few very theoretical
books. behind my back lies 1 meter high mountain of books :)
from practical point of view - its something like srm, at least i think so -
i`ve never used it. from the beginning its designed for php5 new super duper
mechanisms.
by now you probably realized why i`ve showed up in this thread - ability to
manage components flexible is crucial in my project. i need for example way
to detect class name collisions before compiler dies with error - there is
no way to control naming conventions for components. i thought about some
nasty ideas like forcing names in HIVE_UUID form, but as you surely
understand - its horrible solution. probably i`ll have to use second process
to load component and use reflection to check for collisions before loading
in main app server process.
rash
ps. no thread support sucks :]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
