On May 25, 2011, at 08:42:18, Peter Gillard-Moss wrote: > So I understand that there are three parts: An app which sends messages, a > client that receives messages and a Notification service which receives > messages from the app and forwards/broadcasts them to the client.
The “client” is normally a notification system, although it doesn't have to be. Usually, there are only two parts: The app sending, and the notification system receiving. When setting up forwarding, yes, there are three parts. Normally, all but the app are notification systems (like Growl), with each forwarding on to another until the last one. Each recipient of forwarding is a “client” in GNTP's terminology, as each one subscribes to the server. (This is actually backwards from how Growl works right now: In current GfM, you set each receiving Growl to listen generally and then each forwarding Growl to forward to a specific listening Growl. Brian?) > So now I want to have something where multiple Growl clients (like Growl for > Windows) can register with an end point and receive messages from it. I > presume this is the missing part: the notification system. GfM and GfW are each notification systems. -- 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.
