Aaron Johnson wrote: > I want to do some work regarding messaging* for P5EE and would like > comments on the following: > > What type of messaging systems are in use in your organization? > > What is the most important messaging system in your organization? > > Is someone else is already thinking of doing or done work in this area > that would like to collaborate? > <snip>
The response to this has post has been great. I read over the JMS information and I read over Stem, but this is still not what I am talking about doing. I am looking at how this would be applied that the final level, not the server or backend process. I am focusing on the rules that would determine the message transport and how to determine the sucess of such messaging. There is much more to this then system level messaging, which is what Spread and Stem seem to concentrate on. I am talking about person to person and this will need to extend all the way to VoiceXML. Part of the requirements of P5EE as outlined on Stephen's site is that our solutions need to be long term. I want to apologize in advance for my possible lack of correct usage of terminology. An example of where my head is at is this: The requirement of the application/tool is to message a person when a certain action occurs. The method by which the person is to contacted is stored in rules somewhere. These rules define status codes or other items that are known within current processes and can be added to as new processes are added. So lets say that a cronjob application that updates a database with an XML stream of data for example has a complication. Bob needs to be notified that the process has failed. The send_notification function/method is called and passed only the body of the message. send_notification's job is to read the rules and based on the message body, or possible a secondary parameter, send the message via the correct transport system. Another developer is creating an online email system. He too can tap into the send_notification funciton/method and have his email properly formatted and sent. These are just quick thoughts that in no way explore the depth of difficulty in doing this. There would have to be a parameter system in place to allow for correct handling, but it should also have intelligence to do the right thing or notifiy the developer in an intelligent manner if it can not. My focus is and most likely always will be on making the API (interface) to functions/methods as simple as possible. I feel that it will be the responsiblity of the send_notification to "know" what modules to use, this could be extended by configuration options. Lets say that on load Notification reads the conf file and it indicates that all email is processed by the Qmail module, those modules can be included in P5EE or added by third parties. (is this dispatching?) All of these thoughts stem (no pun intended) from my own desire of getting messages via the correct transport to the correct person with out a lot of thinking on the developers end. Basicly all the developer wants to do in the end is send a chunck of text or a binary blob, they shouldn't have to do a lot of thinking to make it happen. In other words this is what I want to avoid: "In messaging systems the point of communication between applications is the message itself, so a developer using JMS must understand messages.." Aaron Johnson
