> > Jim Morrison [Mailing-Lists] wrote: > > Sniff.. I've kind of got something working... Enough such that one > > httpd can request an XYZ, and if a second httpd comes along a little > > later and requests the same XYZ then it will get it from shared memory. > > I hope you used one of the modules I suggested rather than writing the > whole thing from scratch.
Perrin, No :-) 'course I did. Thanks.. I had a play with the two IPC ones you sent, Shareable and MM.. I settled on IPC::ShareLite for now.. which seems the simplest to use. > > As expected though.. trying to do this with LibXML objects fails.. a > > lot. > > LibXML is an XS module, so that may interfere with serialization. Umm. Ok... Does that mean I'm doomed? (not sure what an XS module is) > > CAVEAT : I know it's probably looked at as a silly idea, but if I could > > keep my parsed stylesheets/xml's shared somewhere I'd save my self > > having to re-parse for every request wouldn't I? . . > > Why don't you try caching the results instead? The CMS we use builds static content.. (is that what you mean?) so it caches the whole site in one go I guess.. never been one for dynamic content ;-).. But there are places where I'm going to need dynamic content - I would like to be able to do this in principle.. I mean, I would like to cache my parsed stylesheets/xml in mem. rather than re-parsing all the time.. And I'm getting some mileage out of experimenting with this anyhow - if it doesn't work for LibXML it looks like it could be very useful for other stuff, and if it ever works bug-free(-ish) I'd like to give something back to all the CPAN-people who've written things I use.. Kindest, Jim.