Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Apache

Journal Micah's Journal: Slashdot-style CMS ... as an Apache module in C 4

Here's a brainfart idea I've had: a project to create an Apache module directly in C for a Slashdot-style CMS system. Rationale:

  • Slashcode consumes a hideous amount of memory and is rather complex.
  • PHP solutions are dog slow due to having to parse boatloads of PHP objects for every HTTP request, and these objects cannot be persistant.

Also, I want to design it to work solely with PostgreSQL. This project would be designed for users who have control of their system software, not your typical PHP/MySQL hosting plan. Standardizing on PostgreSQL would allow for simpler code, use of transactions, use of triggers and stored procedures to make the C code less complex, and undoubtably other advantages.

Another interesting goal is that it would be designed to return XML pages parsed by client side XSLT. This would make templates in the server unnecessary as each user would create his own XSLT to process standard XML data. No, it won't work on every browser right now, but let's design for the future. This design would also allow for minimal data transfer for each request. Since the XSLT would be cached, the header and footer info would only need to be loaded once, not to mention all the HTML formatting. Only the bare data in XML format would be transferred each request.

As much as possible, it should be made such that it could be easily extended by other modules written in C.

This idea is currently just in the "brainfart" stage, but I'm throwing it out for comment.

This discussion has been archived. No new comments can be posted.

Slashdot-style CMS ... as an Apache module in C

Comments Filter:
  • I envision it not necessarily having built in "admin panels", but configuration would mostly be simply through the Apache config file for things like "allow anonymous posting?". Things like the site name and slogan would be in the XSLT. A PHP based front end could be built to edit the config values, which would take effect next time the admin restarted the server (which he could say, every half hour, if one of the users had a config change).

    Perhaps it should require Apache to use a threaded MPM. This sh
    • It's already done. The base technology is called Zope [zope.org], and the best final implementation (but not the only one) of CMF on a top of it is Plone [plone.org].

      Talking about DBMS, by default you Zope persists everything in ZODB (Zope Object-oriented DBms), but you can easily mount (with DBTab) FS, SQL, IMAP and other external persistent storage.

      By the way, RDF/RSS syndication is already provided in Zope/Plone.

      • Well, that's not done in C nor as an Apache module.

        Nevertheless I should probably take a closer look at Plone. It may solve most of the gripes I have about current CMSes.

The key elements in human thinking are not numbers but labels of fuzzy sets. -- L. Zadeh

Working...