Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • After reading the newsletter and browsing the site I still have no idea. The closest I got was that it is a "networking toolkit." One of the haikus in the FAQ mentioned Perl - is that why it's on use.perl.org?

    Sticking with LWP,
    -sam
    • Stem is all pure-Perl, though it does rely on the Event module (which is C).

      It is designed to support asynchronous message-based systems. Does that help?

      Saying that you're sticking with LWP is kind of meaningless. Stem is largely orthogonal to LWP.

      A representative Stem application might be a process that responds to outside requests via a socket, delegates work to multiple child processes (like Apache, perhaps) and then responds to the request.

      The nice thing about using Stem for that is that you would
      • So more like Net::Server than LWP? -sam
        • More like POE. Much more like POE.
          • Re:What is Stem? (Score:3, Informative)

            by uri (2673) on 2002.04.08 15:49 (#6768) Homepage Journal
            Stem and POE cover overlapping problem spaces but have very different architectures. even the POE development people recognize that each has its advantages. in fact when we (stem and poe) get some free tuits, we will make the two systems interact. POE has a much larger code base but it requires you to write more code to actually drive it. stem allows you to configure (not code) the its modules into network applications. complex programs such as inetd (see the demo in the tarball) are done without new coding and no builtin knowledge of how inetd is supposed to work.