On 27 May 2011, at 07:53, Peter Gillard-Moss wrote: > GfM and GfW are each notification systems. > > > Ahh, so I should have my app point to a GfW instance (as per normal) and then > point clients at that GfW instance. Like so > > App > GfW Client <* GNTP Client > > Many thanks >
Yes, but this will only work in a general forwarding case, not on a per-user basis. For that you would have to roll your own forwarder. As I understand it, I think the problem here is because growl as a notification system has been designed such that everything belongs to an owner (user). Notifications come from apps that are being run by a user. The local growl client is being run by a user, and (optionally) is forwarding on to another. In this case, the app serving notifications is not owned by anyone in particular (being a server app), and neither is the local client necessarily. In order to filter notifications for any subscribed clients being forwarded to, I can see two possibilities: 1) Assign the notifications a user, pass that all the way down. 2) Do the user-based assignment only from the subscription level. Both have merits and use-cases, I think. However, 1 would require more changes at the protocol level (notifications require an additional user header, or something). If the protocol were to add a username to the ‘subscribe' message, I think it makes sense if they were added to ‘notify' messages et al as well. Otherwise, if only interested in 2, Peter’s suggestion of user:pass => current password hash works fine. I guess question for devs: Should (optional) user fields be added to the protocol to allow for operation in user-less environments? This could be pretty cool. Eg. what if a bug-tracking website could send me notifications about bug changes, as it does with emails currently? PMs from forums? possibilities… -- 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.
