>>>>> "JNP" == Joshua N Pritikin <[EMAIL PROTECTED]> writes:
JNP> Also, i shouldn't neglect to mention that a major goal for Event
JNP> is to be the common API to which event driven modules/libraries
JNP> are written.
still, i wrapped my object code around event.pm for several
reasons. first, i simplified the api some and made it pure OO and
such. it supports more default values, especially the callback
names. all the higher level stuff uses the stem event layer and never
sees event.pm directly. this was important to me so the advantage of
supporting other low event loops is a bonus.
JNP> The more modules which are written to Event specs, the more easily
JNP> developers can glue applications together without being forced to add
JNP> lots of glue code.
heh. one of our mottos it 'perl is the glue of the net - stem is the
superglue!'
JNP> Event has been well received, but so far there is no Event port
JNP> of LWP, Tk, or CORBA. No doubt there are other popular libraries
JNP> without Event support too.
eventually we will have an LWP equivilent under stem. supporting
multiple parallel protocols is a major design win i want. i have already
laid out some major design points in my brane. LWP::Parallel loses as it
runs its own event loop and is such a load of **** code. LWP isn't
pretty either. stem will be doing a ground up redesign that make all tcp
based protocols use common modules such as state machines and async i/o
which makes adding/modifying them much easier. and you get parallel
execution as a given and not jammed in.
as for corba, stem allows message passing between objects (and messages
can carry objects if you want) so it will be a simpler form of corba.
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
