Command Flow - Revision history

Matt: Reverted edits by Amesycyxa (Talk); changed back to last version by Jmaine

2010-11-26T19:40:04Z

Reverted edits by Amesycyxa (Talk); changed back to last version by Jmaine

Amesycyxa at 08:31, 24 November 2010

2010-11-24T08:31:48Z

Jmaine at 00:27, 24 November 2008

2008-11-24T00:27:27Z

Jmaine at 00:16, 24 November 2008

2008-11-24T00:16:33Z

Kyle at 01:09, 31 January 2008

2008-01-31T01:09:38Z

Kyle: New page: Category:developerDocCategory:EmulatorDocCategory:EngineImplementation This page shows how commands go through the components in the engine. In particular it describes the va...

2008-01-31T00:58:04Z

New page: Category:developerDoc Category:EmulatorDoc Category:EngineImplementation This page shows how commands go through the components in the engine. In particular it describes the va...

New page

[[Category:developerDoc]][[Category:EmulatorDoc]][[Category:EngineImplementation]]

This page shows how commands go through the components in the engine. In particular it describes the various transformations that a single message goes through.

[[Image:commandFlow.png|thumb|800px|none|How a command flows through the engine]]

← Older revision		Revision as of 19:40, 26 November 2010
Line 1:		Line 1:
−	~~----~~
−	<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
−	~~----~~
−	~~=[http://eludevyvema.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=~~
−	~~----~~
−	~~=[http://eludevyvema.co.cc CLICK HERE]=~~
−	~~----~~
−	~~</div>~~
	[[Category:developerDoc]][[Category:EmulatorDoc]][[Category:EngineImplementation]]		[[Category:developerDoc]][[Category:EmulatorDoc]][[Category:EngineImplementation]]

← Older revision		Revision as of 08:31, 24 November 2010
Line 1:		Line 1:
		+	----
		+	<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
		+	----
		+	=[http://eludevyvema.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
		+	----
		+	=[http://eludevyvema.co.cc CLICK HERE]=
		+	----
		+	</div>
	[[Category:developerDoc]][[Category:EmulatorDoc]][[Category:EngineImplementation]]		[[Category:developerDoc]][[Category:EmulatorDoc]][[Category:EngineImplementation]]

@@ Line 12: / Line 12: @@
 #Next the command goes through the [[READERNAME_CommandFormatter.java|command Formatter]], which transforms the message from a sequence of bytes into a command object that can be executed in a [[READERNAME_CATEGORY_Handler.java|handler method]]
 #The Adapter uses the newly formed command object and the command searcher to look up a handler method name in the [[reader.xml]] file.  After it finds the handler method which should process the command, it invokes the handler method using reflection.
-#The handler method processes the command in some specific way.  For example, if the command is 'get taglist' in an alien reader, it will scan the radio and collect the tag information.  The handler method will put any return value into the command object and return back to the adapter.
+#The handler method processes the command in some specific way.  For example, if the command is 'get taglist' in an alien reader, it will scan the radio and collect the tag information. The radio will read the reader's [[TagMemory|tag memory]]. The handler method will put any return value into the command object and return back to the adapter.
 #The adapter now passes the command back through the formatter to turn the command object into a response message.
 #The command formatter will place the outgoing message onto the outgoing message buffer
 #The Buffer will pass the message back through the protocol to add back in a protocol if it needs to be done
 #The TCP Outgoing Buffer will send the response back to the clien

@@ Line 6: / Line 6: @@
 # Commands are sent to the TCP Incomming buffer which is located inside the TCP Socket.  The Stream Reader is a reader-specific class designed to read bytes off of the socket.  It is needed because some types of readers, such as the Alien, use plain text for their commands, so it is easier to use a readLine() method to read from the socket.  Other readers, such as the LLRP reader need to use a readByte() method, because the commands are byte strings.
-#  From there, the command moves to the protocol.  The Protocol is a reader-specific class that performs two functions:
+#  From there, the command moves to the [[READERNAME_Protocol.java|protocol]].  The Protocol is a reader-specific class that performs two functions:
 ## It removes any kind of protocol that the reader uses to communicate, such as HTTP
 ## It is possible for a client to send two commands at once.  If this happens, The protocol breaks up multiple commands and places each one on the Incomming Message Buffer to be processed individually.
 #After a Command is placed onto the Incomming Message Buffer, the buffer notifies the command controller to take off the next command from it
-#Next the command goes through the command Formatter, which transforms the message from a sequence of bytes into a command object that can be executed in a handler method
+#Next the command goes through the [[READERNAME_CommandFormatter.java|command Formatter]], which transforms the message from a sequence of bytes into a command object that can be executed in a [[READERNAME_CATEGORY_Handler.java|handler method]]
-#The Adapter uses the newly formed command object and the command searcher to look up a handler method name in the emulator.xml file.  After it finds the handler method which should process the command, it invokes the handler method using reflection.
+#The Adapter uses the newly formed command object and the command searcher to look up a handler method name in the [[reader.xml]] file.  After it finds the handler method which should process the command, it invokes the handler method using reflection.
 #The handler method processes the command in some specific way.  For example, if the command is 'get taglist' in an alien reader, it will scan the radio and collect the tag information.  The handler method will put any return value into the command object and return back to the adapter.
 #The adapter now passes the command back through the formatter to turn the command object into a response message.

← Older revision		Revision as of 01:09, 31 January 2008
Line 4:		Line 4:

	[[Image:commandFlow.png\|thumb\|800px\|none\|How a command flows through the engine]]		[[Image:commandFlow.png\|thumb\|800px\|none\|How a command flows through the engine]]
		+
		+	# Commands are sent to the TCP Incomming buffer which is located inside the TCP Socket. The Stream Reader is a reader-specific class designed to read bytes off of the socket. It is needed because some types of readers, such as the Alien, use plain text for their commands, so it is easier to use a readLine() method to read from the socket. Other readers, such as the LLRP reader need to use a readByte() method, because the commands are byte strings.
		+	# From there, the command moves to the protocol. The Protocol is a reader-specific class that performs two functions:
		+	## It removes any kind of protocol that the reader uses to communicate, such as HTTP
		+	## It is possible for a client to send two commands at once. If this happens, The protocol breaks up multiple commands and places each one on the Incomming Message Buffer to be processed individually.
		+	#After a Command is placed onto the Incomming Message Buffer, the buffer notifies the command controller to take off the next command from it
		+	#Next the command goes through the command Formatter, which transforms the message from a sequence of bytes into a command object that can be executed in a handler method
		+	#The Adapter uses the newly formed command object and the command searcher to look up a handler method name in the emulator.xml file. After it finds the handler method which should process the command, it invokes the handler method using reflection.
		+	#The handler method processes the command in some specific way. For example, if the command is 'get taglist' in an alien reader, it will scan the radio and collect the tag information. The handler method will put any return value into the command object and return back to the adapter.
		+	#The adapter now passes the command back through the formatter to turn the command object into a response message.
		+	#The command formatter will place the outgoing message onto the outgoing message buffer
		+	#The Buffer will pass the message back through the protocol to add back in a protocol if it needs to be done
		+	#The TCP Outgoing Buffer will send the response back to the clien