Sorry, I'll clarify that architecture again (using the same language as the spec).
>From my understanding there are three components: - Sending application - Notification system - Subscriber In my scenario I envisage this to be structured as so: - My internal app is the sending application, it know nothing about subscribers - Some form of notification system with a single endpoint (most likely an extension to the internal app) which subscribers subscribe to - Vanilla Growl for Windows, OSX, Linux, iPhone etc. client as the subscriber I presume this is a correct architecture? What I don't understand is how to build the notification system or whether something already exists. Peter -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
