Differences between revisions 24 and 53 (spanning 29 versions)
Revision 24 as of 2008-06-29 18:36:08
Size: 1926
Editor: CarlNobile
Comment:
Revision 53 as of 2012-01-15 21:16:36
Size: 1360
Editor: CarlNobile
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
== RESTful Python Web Service using WSGI == [[EPIA|Electronic Parts Inventory Application]]
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.

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.

TODOs:

 * HTTP Digest Authentication.
 * Auto generation tool for creating the global configuration file and some of its dependencies.

[[http:../cgi-bin/viewvc.cgi/RestFramework/|CVS Repository]]
[[RPWS|RESTful Python Web Service using WSG]]
Line 24: Line 8:
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.
Line 25: Line 10:
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. In general the chat server would need some sort of client agent. The backend is an XML-RPC server.
Line 27: Line 12:
[[http:../cgi-bin/viewvc.cgi/chatserv/|CVS Repository]]
[[http://tetrasys.homelinux.org/cgi-bin/viewvc.cgi/chatserv/?root=cvs|CVS Repository]] This is off site.
Line 31: Line 15:
Line 34: Line 17:
[[http:../home/AjaxStub/ajaxstub.py|API Home Page]] [[http://tetrasys-design.net/home/AjaxStub/ajaxstub.py|API Home Page]]
Line 36: Line 19:
[[http:../cgi-bin/viewvc.cgi/ajaxstub/|CVS Repository]]
[[http://tetrasys.homelinux.org/cgi-bin/viewvc.cgi/ajaxstub/?root=cvs|CVS Repository]] This is off site.
Line 40: Line 22:
Line 43: Line 24:
[[http:../home/Linklist|API Home Page]] [[http://tetrasys-design.net/home/Linklist/|API Home Page]]
Line 45: Line 26:
[[http:../cgi-bin/viewvc.cgi/OpenSource/linklist/|CVS Repository]] [[http://tetrasys.homelinux.org/cgi-bin/viewvc.cgi/OpenSource/linklist/?root=cvs|CVS Repository]] This is off site.

Projects

Electronic Parts Inventory Application

RESTful Python Web Service using WSG

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 This is off site.

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 This is off site.

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 This is off site.

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