The PureMVC philosophy doesn’t allow mediators to know about the existence of each other in order to keep coupling within the system as low as possible, and Mediator isn’t an EventDispatcher so you won’t be able to use dispatchEvent.

The correct method is certainly to send a notification - why do you think that is ridiculous?

You shouldn’t really think of notifications as being any different to Flash events; they just happen to be the way that PureMVC implements observable state (they used custom notifications rather than Flash events as PureMVC is also available in languages which don’t implement the Flash event system).

In big applications I will sometimes organise my notifications into seperate classes to keep them together with notifications in the same conceptual area. For example I might have FileNotifications.SAVE_DOCUMENT and VisualNotifications.SHOW_PROGRESS_BAR.

Hope that helps,

Dave

What’s the easiest way for one mediator to call a function in another mediator? I tried to dispatch and event, but I get this error:

“Call to a possibly undefined method dispatchEvent.”

Do I need to call a function in the mediator’s view and dispatch the event from the view (which I can get working)? Or do I need to send a notification? The latter seems ridiculous and the first method seems too convoluted. Seems like you should be able to dispatch an event from the mediator.

I’m not sure - I’ve not had a similar problem. I’d recommend that you download and install Openfire (http://www.igniterealtime.org/projects/openfire/index.jsp) on your local machine and use that as a test Jabber server to start with. This will help you localise whether or not the problem is with your code or jabber.org.

Cheers,

Dave

It’s sad.
Dear Dave, don’t you know what this problem could be about?