[asterisk-commits] oej: branch oej/managergames r174538 - /team/oej/managergames/
SVN commits to the Asterisk project
asterisk-commits at lists.digium.com
Tue Feb 10 05:44:01 CST 2009
Author: oej
Date: Tue Feb 10 05:44:00 2009
New Revision: 174538
URL: http://svn.digium.com/svn-view/asterisk?view=rev&rev=174538
Log:
Adding a manifest for this branch.
Let the games begin!
/O
Added:
team/oej/managergames/README.managergames.txt (with props)
Added: team/oej/managergames/README.managergames.txt
URL: http://svn.digium.com/svn-view/asterisk/team/oej/managergames/README.managergames.txt?view=auto&rev=174538
==============================================================================
--- team/oej/managergames/README.managergames.txt (added)
+++ team/oej/managergames/README.managergames.txt Tue Feb 10 05:44:00 2009
@@ -1,0 +1,41 @@
+Edvina AB
+Olle E. Johansson 2009-02-10
+
+
+
+
+Manager conversion to the new event structure
+---------------------------------------------
+
+The manager events generated by Asterisk modules today basically produce a simple
+string and send that to the manager module for handling.
+
+I would like to start the conversion to a new *INTERNAL* format by adding a new
+manager event call that uses a new structure and support in manager.c for
+converting this to the existing format at transmission to manager port or http server.
+
+When we have this working, we can convert existing modules to the new format and
+start looking at actions/responses, propably starting with the outbound responses.
+
+This will require:
+
+- A review of the event data structures
+ - Do we have the data types we need?
+ - Example: Do we need a definition for host adress - IP or name?
+
+- A review of the event data values - which are string, which are numeric, which are something else?
+
+After discussion with Russell at Fosdem 2009, I don't believe that this will
+be a huge process. We will need help from the community by applying this as a janitor process,
+and I'm sure we'll get the help we need provided we have proper guidelines.
+
+I am also considering adding data types for the various event headers. This is for
+the possibility of sharing events across the event bus to other systems.
+The event structure will need an addition of the system name/eventID for the remote
+system, so we can separate incoming events from local events.
+
+
+This will take some time, as I only can work on this in spare time. Any assistance
+is of course welcome and feedback is gently asked for!
+
+/O
Propchange: team/oej/managergames/README.managergames.txt
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: team/oej/managergames/README.managergames.txt
------------------------------------------------------------------------------
svn:keywords = "Author Date Id Revision"
Propchange: team/oej/managergames/README.managergames.txt
------------------------------------------------------------------------------
svn:mime-type = text/plain
More information about the asterisk-commits
mailing list