OpenACS-on-MSSQL port milestone
I've reached an important milestone in my MSSQL Server port of the openacs data model. The kernel and all unit tests compile and run. This means that I am reasonably confident that I can start using it in client projects.
I'd like to figure out a way in which I don't have to hand-port the whole TCL API (which would not be fun.) Realistically, I don't need to do this, because for the limited data-model re-use scenarios I''m envisioning, rewriting the few procedures in Perl is practical. Not the site-node or apm type stuff, certainly, but the basic community framework is do-able on an as-needed basis.
I wish the TCLScript project was further along: http://tclscript.sourceforge.net/. I could see that being a major shortcut, because I don't think porting the specific AOLServer-isms would be a big deal. I'm doing a lot of intranet-type of work where perlscript calls vbscript. I know it's not a paragon of efficiency, or a model for a high-traffic site, but it works and it's stable.
I guess a more scalable (but somewhat inelegant) option would be to run an XML-RPC-serving instance of AOLServer behind IIS, which would support the community framework pieces that I needed. Exposing individual (hopefully stateless) API procedures wouldn't be too bad, and could be automated to a high degree.
It would mean I'd have to tackle the xql files and the data access API, which is probably worth doing anyway.
11:14:32 AM
|