Hrm, sounds interesting.

So what does Event::RPC do exactly?  Can you post a summary?

--- Begin Message ---
Hi Joshua,

I'm using your great Event module for a couple of years in several 
client/server applications. Thereby a transparent object oriented RPC 
mechanism emerged, based on Event.

I didn't publish this framework yet, apart from as a non-modular part of
user-ready applications (e.g. http://www.exit1.org/dvdrip/, which uses 
Event to control a cluster of video transcoding nodes). But now I'm 
planning to do this and I was wondering about a namespace. Since the 
framework is tightly bound to Event, I'd like to call it Event::RPC.

I crawled through CPAN to see, if anybody published already something 
like this, but found nothing comparable, so the name sounds reasonable 
for me. Event:: is originally your namespace, so I wanted to ask you if
you have any objections against this.

Regards,

Joern

P.S.: it wasn't easy to find a valid email address. I grabbed 
[EMAIL PROTECTED] from the top of the Event ChangeLog, but the 
mail bounced with an unknown host error. With help of Google I found 
your homepage and extracted this address from your GnuPG key - which 
hopefully works... ;)

-- 
 .''`.  Jörn Reder <[EMAIL PROTECTED]>
: :' :  http://www.exit1.org/ http://www.zyn.de/
`. `'
  `-    Debian GNU/Linux -- The power of freedom

Attachment: pgpCSAFOobm2V.pgp
Description: PGP signature


--- End Message ---

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to