On May 17, 2011, at 01:11:17, JupiterMoonBeam wrote: > 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
That sounds right. So if I understand your request correctly, you want GNTP to include a username for the sending application to authorize with. It would have to be optional (i.e., an application can log in with password only or username and password, and the notifications system decides what it wants to accept). As far as we've heard, most usage of Growl on a network is on a single person's or family's network, where all parties are equally trusted and it's easy to tell at least who was using the machine notifications were coming from. The next question is how it should be implemented in the protocol. Perhaps not specify it in the protocol at all, but have the sending application concatenate the username and password together, and have your intermediate notifications system expect this and map each username+password hash to the (subscribed) user to forward to. Thoughts? -- 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.
