From: Eli Green Date: 2001-07-17T12:52:48+09:00 Subject: [ruby-talk:17962] Re: FastCGI for Ruby? > > Also, I was wondering about ruby's current status as far as replacing something > > like WebObjects. Basically, it needs a competent web application server and > > something that can copy the functions of EOF (Enterprise Objects Framework) -- a > > framework for mapping relational databases to objects. (Similar to perl's > > Tangram). > > I've been working on exactly this. IOWA maps pretty closely to > WebObjects; it's a prototype and poorly documented, but people have had > some success with it and if you were interested in helping out I'd be > happy to flesh it out more (a FastCGI interface is one thing that would be > nice, but does mod_fcgi implement the multithreaded protocol yet?). The > EOF side is definitely lacking; I took a very quick run at it once but > we'd need to do some serious work to get it into usable shape. > > IOWA is at http://beta4.com/iowa, and some initial EOF code is at > http://beta4.com/kansas.tgz - let me know what you think. > > Cheers, > Avi Excellent! I took a slightly more detailed look at IOWA, and it looks pretty slick (very similar to WO, which I like .. too bad ProjectBuilder doesn't support ruby =). As for mod_fcgi being multithreaded ... yes and no. Under Apache 1.xx, which is forking, it's irrelevant wether it supports the multiplexing features of the FastCGI protocol, since a new connection will need to be opened from every forked process anyway. Under Apache 2.0, it will become more relevant to support it. One of my concerns (that I have yet to investigate) is wether ID's are properly unique under mod_fastcgi currently ... if they're only unique to each apache process, extra processing needs to be done to store the requests from each accept()ed socket separate from each other. How does mod_iowa compare to fastcgi? I just don't like duplicated effort. =) -- Eli Green Connection closed by foreign host.