From b3a26773ed125122f19e94e5e8a7691a9840efeb Mon Sep 17 00:00:00 2001 From: erickson Date: Wed, 9 Feb 2005 16:42:26 +0000 Subject: [PATCH] updated, removed the userAuth stuff git-svn-id: svn://svn.open-ils.org/OpenSRF/trunk@36 9efc2488-bf62-4759-914b-345cdb29e865 --- doc/OpenSRF-Messaging-Protocol.html | 39 +++++++---------------------- 1 file changed, 9 insertions(+), 30 deletions(-) diff --git a/doc/OpenSRF-Messaging-Protocol.html b/doc/OpenSRF-Messaging-Protocol.html index 4cb8f4e..1eeff04 100644 --- a/doc/OpenSRF-Messaging-Protocol.html +++ b/doc/OpenSRF-Messaging-Protocol.html @@ -13,7 +13,7 @@

- The OILS messaging system works on two different primary layers: the transport layer and the + The OpenSRF messaging system works on two different primary layers: the transport layer and the application layer. The transport layer manages virtual connections between client and server, while the application layer manages user/application level messages. @@ -27,10 +27,11 @@ DISCONNECT.

- STATUS message provide general information to the transport layer are used in different + STATUS messages provide general information to the transport layer and are used in different ways throughout the system. They are sent primarily by the server in response to client requests. Each message comes with - a status and statusCode. The actual status part of the STATUS message is just a helpful message (mostly for debugging). The + a status and statusCode. The actual status part of the STATUS message is just a helpful message + (mostly for debugging). The statusCode is an integer representing the exact status this message represents. The status codes are modeled after HTTP status codes. Currently used codes consist of the following: @@ -40,7 +41,6 @@ 205 STATUS_COMPLETE 307 STATUS_REDIRECTED 400 STATUS_BADREQUEST - 403 STATUS_FORBIDDEN 404 STATUS_NOTFOUND 408 STATUS_TIMEOUT 417 STATUS_EXPFAILED @@ -53,8 +53,7 @@

The CONNECT message initiates the virtual connection for a client and expects a STATUS in return. If the connection is successful, the statusCode for the STATUS message shall be - STATUS_OK. If the authentication fails or if there is not actual authentication information - within the message, the statusCode for the returned message shall be STATUS_FORBIDDEN. + STATUS_OK.

If at any point the client sends a non-connect message to the server when the client is not connected or the @@ -112,10 +111,6 @@ if ( msg.statusCode == STATUS_OK ) OK. continue -if ( msg.statusCode == STATUS_FORBIDDEN ) - - handle authentication failure and attempt another connect if requested - while ( more requests ) { /* you may send multiple requests before processing any responses. For the sake @@ -165,12 +160,7 @@ while( message = recv() ) { return a STATUS with statusCode STATUS_EXPFAILED start loop over - if ( message.type == CONNECT and server is unable to authenticate the client ) - - return a STATUS with statusCode STATUS_FORBIDDEN - start loop over - - if ( message.type == CONNECT and server is able to authenticate user ) + if ( message.type == CONNECT ) return STATUS with statusCode STATUS_OK and continue @@ -225,20 +215,12 @@ while( message = recv() ) { -

Type element

- - 
-
-<oils:userAuth hashseed="237" secret="89dd8c65300d4af126cf467779ff1820" username="bill"/>
-
-
-

CONNECT Message 

 
-<oils:domainObjectAttr value="CONNECT" name="type"/>
-	<oils:userAuth hashseed="237" secret="89dd8c65300d4af126cf467779ff1820" username="bill"/>
+<oils:domainObject name="oilsMessage">
+	<oils:domainObjectAttr value="CONNECT" name="type"/>
 	<oils:domainObjectAttr value="1" name="threadTrace"/>
 	<oils:domainObjectAttr value="1" name="protocol"/>
 </oils:domainObject>
@@ -284,10 +266,7 @@ while( message = recv() ) {
 	<oils:domainObjectAttr value="1" name="protocol"/>
 	<oils:domainObject name="oilsMethod">
 		<oils:domainObjectAttr value="mult" name="method"/>
-		<oils:params>
-			<oils:param>1
-			<oils:param>2
-		</oils:params>
+		<oils:params>[1, 2]</oils:params>
 	</oils:domainObject>
 </oils:domainObject>
 
-- 
2.43.2