Re^2: Time to write a "serious" http server in Perl?

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.

Comment on Re^2: Time to write a "serious" http server in Perl?

Replies are listed 'Best First'.
Re^3: Time to write a "serious" http server in Perl? by chromatic (Archbishop) on Aug 16, 2008 at 19:40 UTC
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]
Re^4: Time to write a "serious" http server in Perl? by jdrago_999 (Hermit) on Aug 17, 2008 at 02:28 UTC
Look at qpsmtpd. Looks good :) Thanks for the tip!	[reply]
Re^4: Time to write a "serious" http server in Perl? by jdrago_999 (Hermit) on Aug 17, 2008 at 17:47 UTC
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]
Re^5: Time to write a "serious" http server in Perl? by chromatic (Archbishop) on Aug 17, 2008 at 22:34 UTC
The only substantive difference I can imagine right now is that HTTP tends to be synchronous and SMTP somewhat more asynchronous. Whether that matters much where the main constraint tends to be network IO, conclusions vary.	[reply]