ITrack/MySQL Message Framework - Revision history

Jmckinstry at 22:22, 8 April 2010

2010-04-08T22:22:19Z

← Older revision		Revision as of 17:22, 8 April 2010
Line 54:		Line 54:

	Message Framework objects are NOT thread-safe. Separate objects may be used in separate threads, though.		Message Framework objects are NOT thread-safe. Separate objects may be used in separate threads, though.

			== Direct Database Manipulation ==
			You are able to use this message framework by directly manipulating the database. This can be useful in scripting and debugging.

			=== Creating a Message ===
			* SELECT `f_message_init`(<recipient handle>);
			* For each data element:
			** SELECT `f_message_attach_data`(<message id>, <'Input'\|'Output'>, '<data name>', '<data value>');
			* SELECT `f_message_post`(<message id>, '<message type>', <has inputs, 'True'\|'False'>, <expects response, 'True'\|'False'>);

			At this point, the message will be available in v_messages for receipt.

			=== Responding to a Message ===
			* View available messages and their data using:
			** SELECT * FROM `v_messages` LEFT JOIN messagedata USING (`messageid`);
			*** If you have a handle, add : WHERE `handle` = '<handle>'
			* SELECT `f_message_claim`(<message id>);
			* For each data element you wish to add:
			** SELECT `f_message_attach_data`(<message id>, 'Output', '<data name>', '<data value>');
			* SELECT `f_message_respond`(<message id>);

			At this point, the message will be available in v_responses for any listeners if the message expects a response, and the message will be closed and removed otherwise.

			=== Closing a Message ===
			* SELECT * FROM `f_message_close`(<message id>);

			This action can be done at any time, and will only cause issue if you close someone else's message after they've copied the message, but before they've claimed it

	[[Category:ITrack/Code]]		[[Category:ITrack/Code]]

Jmckinstry at 18:31, 8 April 2010

2010-04-08T18:31:26Z

← Older revision		Revision as of 13:31, 8 April 2010
Line 50:		Line 50:
	=== Caveats ===		=== Caveats ===
	Errors that occur will most likely be ITSQLError objects that get thrown.		Errors that occur will most likely be ITSQLError objects that get thrown.

			You must create and handle your own MySQL connection object.

			Message Framework objects are NOT thread-safe. Separate objects may be used in separate threads, though.

	[[Category:ITrack/Code]]		[[Category:ITrack/Code]]

Jmckinstry at 18:30, 8 April 2010

2010-04-08T18:30:00Z

@@ Line 2: / Line 2: @@
 == General ==
 == Usage ==
 == Code ==
 === Caveats ===
 [[Category:ITrack/Code]]

Jmckinstry: New page: The MySQL Message Framework is used to create a connection to a message repository. The message repository allows the calling code to create and receive messages from other processes. ==...

2010-04-08T17:45:43Z

New page: The MySQL Message Framework is used to create a connection to a message repository. The message repository allows the calling code to create and receive messages from other processes. ==...

New page

The MySQL Message Framework is used to create a connection to a message repository. The message repository allows the calling code to create and receive messages from other processes.

== General ==

== Usage ==

== Code ==

=== Caveats ===

[[Category:ITrack/Code]]