they can be a URL or a special identifier that indicates to callbacks are specified in one of several formats, similar to imageĭata. these custom attributesĬould be used by the display notification or in the callback (see HTTP headers allow you to add custom headers.

allow the inclusion of custom attributes in addition to the that should allow enough flexibility forĭifferent scenarios (desktop, network notifications, web-based, etc) ( or raw data (similar to the data:// urls image data can be passed in several formats, including using a URL Section of this group if anyone wants to take a look at it ( /group/growl-development/web/ i uploaded a simpleĭescription of what a JSON-based protocol might look like to the Files i haveĪctually been thinking about this topic for quite awhile and will add Than XML, and parsers should be available for every platform. I would second the JSON approach - it is nice and easy, less verbose Than that expand on those thoughts with what might be an appropriate Password) being specified on both ends?' with that password being theĭecryptor for the message, I think. Just need to be able to say, 'Is the same password (or lack of His counter-suggestion was something similar to MIME headers, like this:ĭescription: This thing happened, and I thought you should know.Īny thoughts or preferences for one approach versus the other?Īlso, I have no experience in the production of a secure protocol. The number of bytes to follow were to be interpreted literally, that Necessitating base64 encoding or the like. Notification is the image data, and raw bits and XML don't mix,

However, he pointed out that the majority of the data in a This thing happened, and I thought you should know. Given the wide variety of XML libraries available. (for a human) and straightforward to write and parse in most languages I initially suggested an XML-based protocol, as XML is easy to read Peter and I discussed the protocol a bit off-list already. With (1) and (2), should be straightforward for a wide variety of Potentially sensitive data over the wire. We need to have some form of authentication, preferably withĮncryption of notifications so that there are no concerns with sending The protocol should be relatively easy for both sender and receiver.ģ. What TCP-based networking protocol? That's where this email and you,ġ. Growl and will be continuing to improve networking in general. Growl for Windows comes with several displays or skins built-in, and more can be downloaded from their website.In August, I will be implementing a TCP-based networking protocol for Growl can forward notification to your iPhone, an email address, post to Twitter or even read it aloud!

This is extremely helpful for network administrators. For instance you can configure Growl notifications from client PCs to be forwarded to the server to keep tab of what’s happening on other computers on the network. One interesting feature of Growl is that it allows notifications to be forwarded to another computer on the network. To make this happen you must download and install the appropriate plug-in for the application from the site. Applications must register to send notifications with Growl and once registered, they will appear in the application. When you install and run Growl for the first time, the application tab will be blank. The current list of supported applications include names of like iTunes, Pidgin, Firefox, Foobar2000, Thunderbird, uTorrent, Skype, Outlook and some more.

Growl applications