Adventures in Event Everywhere

So yeah I am smoking the event system though and though. Javascript based on around event system that is directly sending and receiving events to and from the backend. Which is also sending and receiving events from/to the front end. Of which it just has a bunch of event handlers which then create more events that are sent back to the front end, handled by the backend or stuffed on a message bus....

STOP!!!!

Why would anyone in there right mind every do anything like this? One of the problems I am reminded about a lot is that large software gets complex. And trying to keep everything in my head at once doesn't work. I need to break things down. More over I need to have a clean way of slicing up the functionality. The second part of this is that modern applications have server side code and client side code of which they are usually two different languages if not more because of the many mobile platforms ect. So I also would like a clean way to communicate between languages. So both client and server side can agree a protocol of events and data that is going to be passed for those event. Then both client side and server side will write event handlers for all the communication code. This is easy to quickly write communication wrappers that just call function / methods that have registered for event(s).

Pros:

• Simple (conceptually and implementation)
  
• Cross platform
• Design works well with both front end and backend development
• Protocol is quick and easy to be agreed on by developers
  

Cons:

• RESTful urls are bit strange they can be generated based on event names but won't be as clean
• If you don't like event programming then you will hate this
• Can be difficult to debug with many listeners to a single event

At the moment I am thinking about pushing this system into a repository on bitbucket.org since I have Javascript, Flash, Python and Java bindings for it. I think I even can create a C which would cover C, C++ and Objective-C (Iphone).