Kwiki Blog

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.

Describe the new page here.

python-utils

PyTCPWrap - TCP Wrapper for python

Describe the new page here.

Class Hierarchy

Main Classes

IPlesInterface """

• SetUri_PayloadMethod

PStub

• PClientStub
• PServerStub

PConfig

• PClientConfig
• PServerConfig

PUri

PResource

• PDatabase
  • PDbTable
• PDocument
  • PXmlDocument
  • PHtmlDocument

PRecordSet

PRecord

• PDbTableRecord
• PXmlRecord
• PHtmlRecord

PHandler

• PHttpClient
• PHttpServer

PParser

• PUriParser
• PXmlParser
• PHtmlParser
• PSqlParser

PValidator

• PUriValidator
• PXmlValidator
• PHtmlValidator
• PSqlValidator

PStatus

Utility Classes

PDbTableField

PSqlQuery

PProtocol

PAddress

• PUriAddress
• PDbAddress

PParam

Dummy Classes (defined by the implementation language)

• PExtHttpClient, PExtHttpServer
• PString, PInt, PArray

Legend

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

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

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.

• July 2003
  • ples project goes online at Source Forge
  • Launch mailing list and contact people
  • Project planning

• August 2003
  • Specification finalised
  • UML completed

• September 2003
  • The first ples implementation will be a REST interface written in Perl to interface with the PostreSQL database via the popular DBI::DBD modules obtainable from CPAN.
  • Coding of first ples interface (ples-pl.pgsql) commences

• Oktober 2003
  • ples-pl.pgsql alpha released

• November 2003
  • ples-pl.pgsql beta released

• January 2003
  • Project status review