rasdaman c/s protocol

Request structure

The rasj HTTP request to the rasdaman server uses the HTTP POST-Format with the following parameters:

Parameter:	Description:	Required for
Command	Integer value specifying the desired action (e.g. OpenDB, BT, CT, CloseDB ...)	all requests
Database	String value specifying the database	OpenDB, CloseDB
ClientType	Integer value defining the type of the client (at the moment always RasClient)	all requests
ClientID	Integer value specifying the ClientID (currently set to 1 for every client)	all requests
QueryString	String value containing the RasQL query	executeQuery
Endianess	Integer value containing the Client Endianess	only insert queries
NumberOfQueryParameters	Integer value specifying the number of query parameters	only insert queries
QueryParameters	Byte Array containing the query parameters (MDDs) using the following format: Integer String String Integer String String String Long Byte[] objectType objectTypeName typeStructure typeLength domain storageLayout OID dataSize binary data /TD>	only insert queries

Result formats / internal representation:

The result of a HTTP request has one of the following forms:

MDD Collections:


Byte	Byte	String	Long(4Bytes)	resultElement 1					...
				String	String	String	Long(4Bytes)	Byte[]
Result type 1=MDDCollection	Endianess	Collection type	Number of results	BaseType description	Spatial domain	OID	Size of the Binary Data Block	Binary Data Block

Skalar Collections:


Byte	Byte	String	Long(4Bytes)	resultElement 1				...
				String	Long(4Bytes)	Byte[]
Result type 2=SkalarCollection	Endianess	Collection type	Number of results	ElementType description	Size of the Binary Data Block	Binary Data Block

Errors:


Byte	Byte	Long(4Bytes)	Long(4Bytes)	Long(4Bytes)	String
Result type 0=Error	Endianess	Error number	Line number	Column number	Token

Single Integer Value:


Byte	Integer
Result type 3=Integer	Value

OID:


Byte	String	String	Double
Result type 4=OID	system	basename	localOID

Acknowledgement:


Byte
Result type 99=OK