in reply to Time to write a "serious" http server in Perl?

I personally believe that you may be amazed by Continuity! (Ok, not intended to be a "real" solution to your problem, but certainly worth looking at it if you've never done...)

--
If you can't understand the incipit, then please check the IPB Campaign.

Replies are listed 'Best First'.
Re^2: Time to write a "serious" http server in Perl?
by jdrago_999 (Hermit) on Aug 16, 2008 at 19:24 UTC
    I've looked at Continuity before.

    While writing Apache2::ASP it became apparent to me why ASP.Net went with an event-based model (which Continuity reminds me of). Of course event-based models depend on a proper server-side DOM. Server-side DOM (such as ASP.Net has) is complicated and does not seem to be very popular.

    Any project of this kind is, as perrin put it, "not to be taken lightly." Along similar lines, I would also like to see a Perl SMTP server (that also does not depend on Apache httpd). A topic for another thread I suppose.
[reply]
      Along similar lines, I would also like to see a Perl SMTP server (that also does not depend on Apache httpd).

      Look at qpsmtpd.

[reply]
        Look at qpsmtpd.
        Looks good :)

        Thanks for the tip!
[reply]
        Why would qpsmtpd be an acceptable use of Perl as a network server, while an http server would not be acceptable?

        Is it simply that smtp servers have a finite number of behaviors, while http servers tend to have a much more broad range of possible uses - so that the server cannot be optimized for every kind of situation?
[reply]

In Section Meditations