> -----Original Message----- > From: [email protected] > On Behalf Of Henning Michael Møller Just
> >Michael Ludwig wrote: > > * ASP/PerlScript - looks promising > > We tried this in the early ages of ASP. The main problem for us was > that when things failed it could be in the MS chain of code and we'd > be stuck with a strange error code. Stability under heavy load was an > issue, back then. I don't know about know... I hope I'll get time to explore this soon. > > * PerlEx 3.0 - ditto (but see my thread on the DCOM issue) > > We use this almost exclusively (unless we are doing some COM work with > a single-threaded component, then we use PerlIS). It performs > brilliantly and once you get your head around the persistent code and > data thing, you are off. We have experienced some problems under > extreme loads, though. Many people do, with various technologies. :-) We won't have to handle extreme load, so that doesn't scare me. I just want the site to appear somewhat snappier. Unsurprisingly, CGI will never make that happen. It is reassuring to me to get feedback from people actually using this technology. Much appreciated! > Did you find a solution to you DCOM issue? Did you try to run the > sync-password script to see if it at least is the right symptom? Not yet. But I'll get back to this issue and keep the list updated. > > * PerlIS - don't know yet > > Works very well and if you use code that cannot be run in > multi-threaded environments or that rely on a complete cleanup between > two iterations, this could be the right tool. But if you load a bunch > of modules everytime it may not give you the performance boost you are > looking for... I'll give this a try, too. Thanks for your feedback! Gruß aus Hamburg! -- Michael Ludwig _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
