https://github.com/bustardcelly/as3couchdb

An ActionScript 3 clientside API for interacting with a CouchDB instance.
https://github.com/bustardcelly/as3couchdb

Last synced: 3 months ago
JSON representation

An ActionScript 3 clientside API for interacting with a CouchDB instance.

• Host: GitHub
• URL: https://github.com/bustardcelly/as3couchdb
• Owner: bustardcelly
• License: mit
• Created: 2010-03-03T15:05:50.000Z (over 14 years ago)
• Default Branch: master
• Last Pushed: 2010-11-19T14:20:34.000Z (almost 14 years ago)
• Last Synced: 2024-05-06T10:35:22.260Z (6 months ago)
• Language: ActionScript
• Homepage: http://custardbelly.com/blog/?page_id=127
• Size: 13.3 MB
• Stars: 39
• Watchers: 4
• Forks: 3
• Open Issues: 4
• Metadata Files:
  • Readme: README.markdown
  • License: LICENSE

Awesome Lists containing this project

• awesome-actionscript-sorted - as3couchdb - An AS3 clientside API for interacting with a CouchDB instance. (Networking / Database)

README

        
# License

See the accompanying LICENSE file.

# About

as3couchdb is an ActionScript 3 clientside API for interacting with a CouchDB instance.

as3couchdb at its core is a library to perform CRUD requests on a CouchDB instance. There are two basic entities

on which these requests are made - Database and Document - though the library includes making ancillary request

on the CouchDB instance itself as well (such as listing all available databases).

as3couchdb aims to address performing CRUD requests with ease by exposing correlating methods on the models for

Database and Document directly. To resolve this goal, custom metadata is required for these models that relate

to the url of the CouchDB instance, the database name, the target mediating class between the model and the service,

and the base request instance that communicates with the service. These are explained in futher detail within the Usage section.

# Requirements

The following libraries are required to compile the as3couchdb library project:

## as3corelib

The as3couchdb library requires the as3corelib project (found at [http://code.google.com/p/as3corelib/](http://code.google.com/p/as3corelib/)).

The classes from the as3corelib project that as3couchdb utilizes is SHA1 for generating unique ids

on the client side, and JSON for serializing objects for CouchDB service communication.

## as3httpclient

The as3couchdb library requires the as3httpclient project (found at [http://code.google.com/p/as3httpclientlib](http://code.google.com/p/as3httpclientlib)).

as3couchdb utilizes the as3httpclient API to make proper PUT and DELETE requests on the CouchDB instance.

as3httpclient has a dependency on the following libraries: as3corelib and as3crypto.

## as3crypto

The as3crypto library is used by the as3httpclient (see above requirement).

as3crypt can be found at [http://code.google.com/p/as3crypto/](http://code.google.com/p/as3crypto/)

# Usage 

At the core of as3couchdb are models representing two basic entities within a CouchDB instance - 

a Database and a Document. A CouchDB instance can hold many Databases and Databases can hold many Documents.

In as3couchdb, these entity models have their own methods for performing CRUD requests on a CouchDB instance.

As such, the CouchDatabase, CouchDocument and CouchUser classes allow for custom entity models that contain the business objects that perform these requests.

## CouchModelEntity

The CouchModelEntity class holds properties related to a target database within a CouchDB instance, as well as the business objects that are the basis of transactions.

The role of the CouchModelEntity object is to wire up the associated service mediator for the target model (CouchDatabase, CouchDocument and CouchUser) upon instantiation of a new instance of that model.

The model uses the service mediator to make requests in relation to its exposed action (CRUD) methods.

as3couchdb allows for this wiring to happen by either supplying a custom CouchModelEntity upon instantiation of a model, or by declaring custom metadata for the model class. The metadata directly relates to the properties of a custom CouchModelEntity.

The optional annotations are as follows:

## DocumentService

The DocumentService metadata declares to the url of the CouchDB and the target Database name.

In the following example, the url points to the localhost at port 5984 (the default for CouchDB)

and the database 'contacts'. Any requests made will be perfomed on the 'contacts' database at the CouchDB location.

    [DocumentService(url="http://127.0.0.1:5984", name="contacts")]

## ServiceMediator

The ServiceMediator metadata declares the mediating class between a model and the service. The CouchDatabase

and CouchDocument models calls methods on this mediator to make CRUD requests.

 

    [ServiceMediator(name="com.custardbelly.as3couchdb.mediator.CouchDatabaseActionMediator")]

## RequestType

The RequestType metadata delcares the interfacing request class with the service. The ICouchRequest implementation

is handed to the ServiceMediator in order to establish the proper handling of requests from the service.

The main purpose of the RequestType is to handle multiple runtimes and there URLRequest restrictions.

The Flash Player for AIR supports PUT and DELETE requests, but such requests are not available in the web-based

Flash Player. As such, HTTPCouchRequest is available in as3couchdb and uses the as3httpclient library to make the

requests over a socket. Other implementations are ExInCouchRequest which uses ExternalInterface.

    [RequestType(name="com.custardbelly.as3couchdb.service.HTTPCouchRequest")]

The CouchDatabase and CouchDocument models extend CouchModel which uses a CouchModelEntity to parse these annotations

and wire the models up to perform requests by calling methods on the model themselves.

The models are extensions to EventDispatcher and the ServiceMediator handles dispatching the appropriate events

related to response from the CouchDB service. You can listen for these corresponding CRUD events on the models as well

as basic result and fault events.

# Examples #

To start off, you would create custom models in your application that extend CouchDatabase and CouchDocument.

The following is an example of a custom CouchDatabase model using annotations:

    [DocumentService(url="http://127.0.0.1:5984", name="contacts")]

    [ServiceMediator(name="com.custardbelly.as3couchdb.mediator.CouchDatabaseActionMediator")]

    [RequestType(name="com.custardbelly.as3couchdb.service.HTTPCouchRequest")]

    public class ContactDatabase extends CouchDatabase

    {

      public function ContactDatabase()

      {

        super();

      }

    }

The following is an example of instantiating a CouchDatabase with a custom CouchModelEntity:

	var mediator:ICouchActionMediator = new CouchDatabaseActionMediator();

	var request:IServiceRequest = new HTTPCouchRequest();

	var entity:CouchModelEntity = new CouchModelEntity( "http://127.0.0.1:5984", "contacts", request, mediator );

	var database:ContactDatabase = new ContactDatabase( entity );

	database.addEventListener( CouchActionType.CREATE, handleDatabaseReadCreate, false, 0, true );

	database.createIfNotExist();

	...

	protected function handleDatabaseReadCreate( evt:CouchEvent ):void

	{

		var result:CouchServiceResult = evt.data as CouchServiceResult;

		var database:ContactDatabase = result.data as ContactDatabase;

	}

The following is an example of a custom CouchDocument model using annotations:

    

    [DocumentService(url="http://127.0.0.1:5984", name="contacts")]

    [ServiceMediator(name="com.custardbelly.as3couchdb.mediator.CouchDocumentActionMediator")]

    [RequestType(name="com.custardbelly.as3couchdb.service.HTTPCouchRequest")]

    	

    [Bindable]

    public class ContactDocument extends CouchDocument

    {

    	public var firstName:String;

    	public var lastName:String;

    	public var email:String;

    	

    	public function ContactDocument()

    	{

    		super();

    	}

    }

    

The following is an example of instantiating a CouchDocument with a custom CouchModelEntity:

	var mediator:ICouchActionMediator = new CouchDatabaseActionMediator();

	var request:IServiceRequest = new HTTPCouchRequest();

	var entity:CouchModelEntity = new CouchModelEntity( "http://127.0.0.1:5984", "contacts", request, mediator );

	var document:ContactDocument = new ContactDocument( entity );

	document.addEventListener( CouchActionType.CREATE, handleDocumentCreate, false, 0, true );

	document.create();

	...

	protected function handleDocumentCreate( evt:CouchEvent )

	{

		var result:CouchServiceResult = evt.data as CouchServiceResult;

		var document:ContactDocument = result.data as ContactDocument;

	}

The following is an example of a CouchUser model using annotations:

  

    [DocumentService(url="http://127.0.0.1:5984", name="contacts")]

    [ServiceMediator(name="com.custardbelly.as3couchdb.mediator.CouchSessionActionMediator")]

    [RequestType(name="com.custardbelly.as3couchdb.service.HTTPSessionRequest")]

    public class ContactUser extends CouchSession

    {

    	public function ContactUser( username:String = null, password:String = null )

    	{

    		super( username, password );

    	}

    }

    

The following is an example of instantiating a CouchUser with a custom CouchModelEntity:

	var mediator:ICouchActionMediator = new CouchDatabaseActionMediator();

	var request:IServiceRequest = new HTTPCouchRequest();

	var entity:CouchModelEntity = new CouchModelEntity( "http://127.0.0.1:5984", "contacts", request, mediator );

	var user:ContactUser = new ContactUser( entity );

	user.addEventListener( CouchActionType.CREATE, handleUserCreate, false, 0, true );

	user.addEventListener( CouchActionType.LOGIN, handleUserLogin, false, 0, true );

	user.signUp();

	...

	protected function handleUserCreate( evt:CouchEvent )

	{

		var result:CouchServiceResult = evt.data as CouchServiceResult;

		var user:ContactUser = result.data as ContactUser;

		user.login();

	}

	protected function handleUserLogin( evt:CouchEvent )

	{

		// persistant session has been created and will be used on any further transactions with the CouchDB instance.

	}

Once a CouchUser has been logged in, any subsequent request on documents and databases will be based on the current session. as3couchdb handles renewing

a session after a defined time lapse (the default time lapse for CouchDB is 10 minutes. This can be modified in the CouchDB instance).

CouchUser is required if you are not running what is referred to as an "admin party" on your CouchDB instance. This means there are no administrators defined for your CouchDB instance,

and any one can make any type of transaction. Once you have set up the CouchDB instance to have at least on administrator, that administrator must be logged in (using CouchUser) and a valid session available in order

to signUp() new CouchUser objects and to createIfNotExists() new CouchDatabase objects.

## Further Examples

The following is an example of accessing all the documents within the ContactDatabase:

  

    var database:CouchDatabase = new ContactDatabase();

    database.addEventListener( CouchActionType.CREATE, handleCouchDatabaseReady );

    database.createIfNotExist();

    

    private function handleCouchDatabaseReady( evt:CouchEvent ):void

    {

    	database.addEventListener( CouchActionType.READ_ALL, handleReadAllDocuments );

    	// Pass the class type to resolve payload documents to.

    	database.getAllDocuments( "com.custardbelly.couchdb.model.ContactDocument" );

    }

    		

    private function handleReadAllDocuments( evt:CouchEvent ):void

    {

    	database.removeEventListener( CouchActionType.READ_ALL, handleReadAllDocuments );

    	

    	var contacts:ArrayCollection = new ArrayCollection();

    	var contactList:Array = ( evt.data as CouchServiceResult ).data as Array;

    	var i:int = contactList.length;

    	while( --i > -1 )

    	{

    		contacts.addItem( contactList[i] );

    	}

    }

To create a new document in CouchDatabase:

    var contact:ContactDocument = new ContactDocument();

    contact.firstName = firstNameField.text;

    contact.lastName = lastNameField.text;

    contact.email = emailField.text;

    contact.addEventListener( CouchActionType.CREATE, handleContactSave );

    contact.addEventListener( CouchEvent.FAULT, handleContactFault );

    contact.create();

The create() method is used for Create and Update. The read() method Reads the document from the

database and populates the model. The update() method saves any changes to the database instance.

The remove() method Deletes the document from the database.