>>>>> "AT" == Adam Turoff <[EMAIL PROTECTED]> writes:
AT> (apologies for showing up late for the party...) AT> On Tue, Nov 20, 2001 at 08:18:13AM -0500, Chris Winters wrote: >> uri guttman has a product called Stem that has some overlap with >> message queues/systems in general. He gave a presentation on it at >> YAPC::NA 2001. He's focusing more on large-scale network management, >> but the architecture is very flexible. I'm pretty sure it's not GPL, >> but it's a good source of inspiration in how to tackle synchronization >> problems, etc. AT> I don't think stem is gpl'd, but I'm 99.44% positive it's an AT> all-open source all-Perl framework. i am the process of gpl'ing it now. it will be in the next release which is due in a couple of weeks. also stem has a broad range of uses but we are focusing on marketing sysadmin stuff for development projects. it can be used as a backbone in almost any networking or messaging environment. it does overlap with some of POE and i am in touch with POE people and we will sometime soon get them interacting. in fact one goal i have is to piggyback on POE's low level event loop which works on winblows which is a wide open market for open source messaging systems. also some of the work i am currently finishing is fairly unique from what i can tell. i have factored out the code that supports cloning of objects and their registration in stem along with their associated i/o and networking. this means you can create your own custom objects (stem cells) and focus on their specific needs and still easily support cloning them on demand and as well as other useful resources. this lowers the entry barrier for creating new complex networked objects. in most other systems you have to do all that extra coding by hand for each new object/class. this is not a trivial thing to do and IMNSHO my solution is fairly elegant and stable and only perl could have supported such neat hacking. :) AT> Uri has been working on stem for years, and it's a solution in AT> search of a problem. He's been fighting hard (and succeeded) to AT> improve Event.pm (and possibly Poe?) to build simple, reliable AT> messaging systems. The first example I saw was a 5 line stem AT> program that did something interesting like a telnet client or a AT> chatbot; most of those 5 lines were setup. AT> If stem isn't the core of the solution to P5EE messaging, it's AT> probably tweaking the same knobs and buttons... all messaging systems are fundamentally the same. what i have tried to do with stem is to make it the simplest such system to use and configure. in many common cases there is no need for any programming at all. that is not the case with almost any other messaging system. in the lower level, stem's internal api is also simpler to use than most others. if you have any questions about how stem could be integrated into p5ee (just found the p5ee.perl.org site) messaging, feel free to contact me directly. if you want to know when the new release is out, check out the news on the web site or email me and i will let you know. i expect to announce this release on many sites such as use.perl.com, freshmeat, etc. i can announce it to the p5ee list too. do you think i should subscribe to that list? i will browse the archives soon. thanx, uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com -- Stem is an Open Source Network Development Toolkit and Application Suite - ----- Stem and Perl Development, Systems Architecture, Design and Coding ---- Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
