On Thu, 2 May 2002, Ted Neward wrote: > Just in case people are wondering, "Hmm, what's an interesting project I > could do with Rotor?", I came up with a few ideas that may or may not be > feasible--I'd love to do them but I have zero time. > > 1) Write an Apache module to host Rotor and managed-code modules, sort of a > servlet/ASP.NET mechanism. (Since ASP.NET isn't a formal part of the Rotor > release, you'd have to provide equivalent functionality.)
That's what I was trying to work on with embedding Rotor, but I'm still stuck on the details of putting it into a library without the problems I described here: http://discuss.develop.com/archives/wa.exe?A2=ind0204d&L=dotnet-rotor&F=&S=&P=374 If someone out there can take care of putting Rotor into a library, I can build an Apache module that makes it do cool stuff. Of course, there's the question of what the Rotor shared library will expose. Would it be possible to duplicate the functionality of the existing ffi? I have to admit I don't know much about the ffi interface except for that one example in the tarball, but I do know that if you give me a library and a header file, I can probably get Apache talking to it (at a previous job, I developed a fairly complex Apache module in C, and it wouldn't take me much time to get back up to speed with the internals). Cheers, Brian
