![]() ![]() 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. We will need each beta to atleast file 7 bug reports during the initial period to be eligible for the next steps & the Free Subscription.In August, I will be implementing a TCP-based networking protocol for Rules When you apply please make sure that you can comply with the schedule above. 5th May : Beta 1 of J!Growl released to Beta testers 10th May: Beta 2 release to Beta testers based on reports to date. 4th May : Application process closes & Selected Beta testers are sent access details to tracker. We are giving out a 6 Month Subscription of the extension when it is released to all Beta testers.Ģ9th April : Open up application process. Currently J!Growl Ships with Plugins to show alerts for "User Login & Logout" & "JomSocial Private Message Received " Please click on read more to see the Beta testing schedule & to apply as a Beta tester. We shall be selecting a total of 10 beta testers from the applications. We are into the Beta Version now & want some beta testers to come in & help us test the system on Production or near Production websites. See details here : J!Growl - Realtime Notifications for Everything!. With J!Growl, it is possible to send real time notifications of events on the website when they are online. ![]() The latest entry in the Techjoomla Labs, J!Growl, is a extensible live alerts framework for Joomla sites that allows admins to set alerts for any number of events which are extensible via plugins.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |