Differences between revisions 24 and 31 (spanning 7 versions)
Revision 24 as of 2008-06-29 18:36:08
Size: 1926
Editor: CarlNobile
Comment:
Revision 31 as of 2008-08-26 15:53:04
Size: 2094
Editor: CarlNobile
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
I am currently working on a RESTful interface to be used mainly as the framework for web services. Since it is WSGI compliant it can be used with any WSGI server. I would recommend [[http://code.google.com/p/modwsgi/|mod_wsgi]] as it is extremely fast, light weight, and easy to deploy. I am currently working on a RESTful interface to be used mainly as the framework for web services. Since it is WSGI compliant it can be used with any WSGI server. I would recommend [[http://code.google.com/p/modwsgi/|mod_wsgi]] as it is extremely fast, light weight, easy to deploy and you get all the benefits of Apache.
Line 14: Line 14:
 * A User account example site.  * A User account example site using SQLite.
 * XML serialized/deserializer.
Line 19: Line 20:
 * Auto generation tool for creating the global configuration file and some of its dependencies.  * Auto generation tool for creating dependencies for the global configuration file.
Line 23: Line 24:
[[http:/wiki-htdocs/tetrasys-external/WSGIRestfulDocs/index.html|API Docs]]
Line 25: Line 28:
I have never officially released this code as open source, however, if I get enough encouragement I may. It was basically a medium for testing out a few thoughts, but is a very functional Chat Server. The only client works on the command line, but shows what would need to be done for any client. It would need some sort of client agent or maybe Ajax. The backend is an XML-RPC server. I have never officially released this code as open source, however, if I get enough encouragement I may. It was basically a medium for testing out a few thoughts, but is a very functional Chat Server. The only client available is a command line app., but shows what would need to be done for any client.

In general the chat server would need some sort of client agent. The backend is an XML-RPC server.

Projects

RESTful Python Web Service using WSGI

I am currently working on a RESTful interface to be used mainly as the framework for web services. Since it is WSGI compliant it can be used with any WSGI server. I would recommend mod_wsgi as it is extremely fast, light weight, easy to deploy and you get all the benefits of Apache.

Done or working on as of June 29, 2008:

  • Basic WSGI framework
  • HTTP Authentication (Basic only for now)
  • User authorization (using the backend of your choice)
  • Accept request header redirection to the representation of your choice.
  • Logging independent of sys logs.
  • A User account example site using SQLite.
  • XML serialized/deserializer.

TODOs:

  • HTTP Digest Authentication.
  • Auto generation tool for creating dependencies for the global configuration file.

CVS Repository

API Docs

Chat Server

I have never officially released this code as open source, however, if I get enough encouragement I may. It was basically a medium for testing out a few thoughts, but is a very functional Chat Server. The only client available is a command line app., but shows what would need to be done for any client.

In general the chat server would need some sort of client agent. The backend is an XML-RPC server.

CVS Repository

AjaxStub

This API provides a way to auto generate JavaScript stubs in your HTML that communicates with a Python web service. It is essentially an RPC style service.

API Home Page

CVS Repository

Doubly Linked List API

This is one of my first open source projects and is still seeing quite a few downloads. It's an API for a doubly link list written in C.

API Home Page

CVS Repository

ProjectsPage (last edited 2012-01-15 21:31:03 by CarlNobile)