Difference between revisions of "Modjs"
From Fernseher
Jump to navigationJump to search
| Line 10: | Line 10: | ||
---- | ---- | ||
Things we should have: | Things we should have: | ||
*Class for MIME objects and MIME headers. [MimeObject API] [MimeHeader API] | *Class for MIME objects and MIME headers. [[MimeObject API]] [[MimeHeader API]] | ||
*Object with server info (environment, log functionality) [server API] | *Object with server info (environment, log functionality) [[server API]] | ||
*Object with request info (request string (full and broken up), incoming mime object, maybe cookies already broken up, etc.) [request API] | *Object with request info (request string (full and broken up), incoming mime object, maybe cookies already broken up, etc.) [[request API]] | ||
*Object with response info (outgoing mime object, print functionality, obstack stuff, way to set headers, etc) [response API] | *Object with response info (outgoing mime object, print functionality, obstack stuff, way to set headers, etc) [[response API]] | ||
*File class extensions, if needed [File API] | *File class extensions, if needed [[File API]] | ||
*Better include support (add to File) | *Better include support (add to File) | ||
*MySQL/SQLite classes and support (new classes probably needed here) | *MySQL/SQLite classes and support (new classes probably needed here) | ||
*system call support (put this on server) | *system call support (put this on server) | ||
*image manipulation support (new classes probably needed here) | *image manipulation support (new classes probably needed here) | ||
*json support (maybe just some quick functions on the response/request ? or maybe better as a global) | *json support (maybe just some quick functions on the response (encode) /request (decode) ? or maybe better as a global) | ||
*curl support (new class probably, using MIME stuff to send and receive) | *curl support (new class probably, using MIME stuff to send and receive, probably wrapped by request/response like objects.. maybe they should be classes, too.) | ||
Things the module should do if it can: | Things the module should do if it can: | ||
Revision as of 12:44, 9 January 2009
modjs.org has the rudiments of an apache module to handle server side javascript using SpiderMonkey.
SpiderMonkey APIs and a tutorial. Apache Module APIs and a tutorial.
Would like MIME support, a global request/response object (both MIME trees I think), SQLite and MySQL support, and File IO Support (if its not already there). Also should have support for including other javascript sources. mod_js has an example for includes and some of the request/apache stuff. SpiderMonkey has an example shell that shows some support for File objects I think.
Would be nice to have libGD and/or ImageMagick support (EXIF too, if possible), as well as some sort of curl library to get to other sites to do stuff.
Things we should have:
- Class for MIME objects and MIME headers. MimeObject API MimeHeader API
- Object with server info (environment, log functionality) server API
- Object with request info (request string (full and broken up), incoming mime object, maybe cookies already broken up, etc.) request API
- Object with response info (outgoing mime object, print functionality, obstack stuff, way to set headers, etc) response API
- File class extensions, if needed File API
- Better include support (add to File)
- MySQL/SQLite classes and support (new classes probably needed here)
- system call support (put this on server)
- image manipulation support (new classes probably needed here)
- json support (maybe just some quick functions on the response (encode) /request (decode) ? or maybe better as a global)
- curl support (new class probably, using MIME stuff to send and receive, probably wrapped by request/response like objects.. maybe they should be classes, too.)
Things the module should do if it can:
- Cache compiled javascript code?
- Stay alive? Might already do this...
- Cached javascript context? Would this make sense?
- Cached session stuff? Do I really want/need this?
