Re: mod_ruby, concurrency, IPC, and object caching.
"Kirk Haines" <[email protected]> Mon, 9 Aug 2004 22:14:36 -0400
| Newsgroups | gmane.comp.apache.mod-ruby |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 5 Aug 2004 16:34:42 -0700, Zallus Kanite wrote > This is more of a design question than anything, but, since mod_ruby > allows for persistant objects within libraries, I thought I would > ask: I'm writing Yet Another web framework/CMS, and was wondering > what the best solution would be to avoid having disparate versions > of an object (say, a DB row in a user table) being held in each of > Apache's children. Solutions I've thought of: . . . > 3. Somehow maintain IPC between all the children, perhaps making one > (possibly the first to serve a request) responsible for holding a > table of such things. > > I can't really think of how to do this; has anyone had any > experience with something like this? You haven't gotten many (any?) replies, so I figured I'd weigh in here. Given the model of keeping your CMS code in Apache under mod_ruby, I'd look closely at doing #3 with Drb. Drb is remarkably easy to use, and my hunch is that you could apply it to your task without a great deal of trouble. Kirk Haines