Kwiki Blog

 
Thu Jul 17 13:50:42 2003 PlesContact

This project was initiated by Eugene Coetzee of Reedflute Software Solutions.

Ples is actively developed and maintain by the OpenCafe.

Contact the project manager at info@opencafe.co.za or via the formal Source Forge channel.

Thu Jul 17 13:50:13 2003 PlesPhp

Describe the new page here.

Thu Jul 17 13:49:51 2003 PlesPython

python-utils

PyTCPWrap - TCP Wrapper for python

Thu Jul 17 13:49:27 2003 PlesPerl

Describe the new page here.

Thu Jul 17 13:48:57 2003 PlesUml

Class Hierarchy

Main Classes

IPlesInterface """

PStub

PConfig

PUri

PResource

PRecordSet

PRecord

PHandler

PParser

PValidator

PStatus

Utility Classes

PDbTableField

PSqlQuery

PProtocol

PAddress

PParam

Dummy Classes (defined by the implementation language)

Legend

  • The notation used does not comply with any specific 'standard' of UML notation
  • 'P' prefixed to class name = Ples class

.....................................................

Thu Jul 17 13:48:19 2003 PlesUml

Class Hierarchy

Main Classes

IPlesInterface """

PStub

PConfig

PUri

PResource

PRecordSet

PRecord

PHandler

PParser

PValidator

PStatus

Utility Classes

PDbTableField

PSqlQuery

PProtocol

PAddress

PParam

Dummy Classes (defined by the implementation language)

Legend

  • The notation used does not comply with any specific 'standard' of UML notation
  • 'P' prefixed to class name = Ples class

.....................................................

Thu Jul 17 13:47:44 2003 PlesSpecification

ples intends to provide a common conceptual framework for developing REST interfaces to SQL databases in the Perl, Python and PHP scripting languages. The modules will first be designed and defined in terms of UML to provide a language independent framework to work from. The "UML" notation used doesn't necessarily comply with any recognised standard and has been modified so that it can easily be published and edited on-line.

The following basic functionality will be rendered by a ples database interface :

  1. Navigation from root data objects (databases) to tables and associated tables.
  2. Viewing of data from a table through the HTTP GET method.
  3. Addition of new data to a table through the HTTP PUT method.
  4. Updating of existing data in a table through the HTTP POST method.

Example of a Java REST interface to a SQL database

Have a look at the screen shots from sqlrest project to get an idea of how the interface should work.