On Thursday, July 7, 2011 1:14:39 PM UTC-5, Chris Forsythe wrote: > > > > On Thu, Jul 7, 2011 at 1:11 PM, Neal Horman <[email protected]> wrote: > >> >> >> On Thursday, July 7, 2011 11:40:53 AM UTC-5, Peter Hosey wrote: >>> >>> On Jul 7, 2011, at 09:29:37, Neal Horman wrote: >>> > em... ok, just so I understand clearly.... >>> > >>> > 1.2.x currently has the udp protocol ? which I have made extensive use >>> of, but is old, and obscurely documented here. >>> > >>> > 1.3.x won't have the udp protocol, but will have GNTP ? >>> >>> Yes. >>> >>> > Not sure where it is documented as there are no references on the web >>> site, which is 1.2.x centric and has no road map at all. >>> >>> The roadmap is on our Google Code project site: >>> >>> http://code.google.com/p/**growl/wiki/RoadMap<http://code.google.com/p/growl/wiki/RoadMap> >>> >>> We haven't updated it for our App Store plans yet, though. >>> >>> > 2.x won't have either ? >>> > >>> > So there will be no way to have local network based notifications ? >>> >>> Incorrect. GNTP is the new protocol for 1.3 and all future versions. >>> >> Thanks for the quick and clear response. >> >> Looking at the current code in the GoogleCode, it appears to be over year >> old, and there is nothing there for GNTP. >> Following the clones trail, there are some changes in hiimerik-lrgrowl >> that appears to have some GNTP stuff, and also appears to be really old. >> >> Looking through some of the "Issues" tickets, it appears that somewhere >> hidden in a secret place there is a separate developers repository that >> holds all of the new "good" stuff, and GC is merely a published code >> repository that is 1.2.x based. >> >> So, how does someone actually get involved with Trunk, Tags, and Branch >> (to use a svn'ism) code base so as to be able to get a fix on the state of >> the project ? >> >> One of the issues in tracker (or wiki, don't remember now) states that >> GNTP needs docs. >> Well I'm might be interested in trying to participate in that to be able >> to gain an understanding of the protocol so that I can re-write my network >> server interface to do GNTP notifications, but I don't know where to go from >> here.... >> >> help, left stranded on the side of the road! >> > > We had to lock the repo down until 10.7 comes out (not the gm to devs, the > official release) to avoid nda violations. >
This makes sense now since I've also signed the NDA. > The gntp spec is here: > > http://www.growlforwindows.com/gfw/help/gntp.aspx > Interesting that it is a GfW spec. I think I remember seeing this a few years back, but payed no attention to it because it wasn't officially supported by Growl, and then I implemented the upd protocol. One of the things that GNTP doesn't take into consideration is broadcast based notifications because it's tcp centric, which udp handles by nature. This could possibly be handled by taking advantage of Bonjour notifications, assuming that they are implemented by the growl notification application clients, but if there are a lot of them, then there is a lot more network traffic, and a lot more work on the notification producer side to keep track of all the clients (sockets, passwords, etc...) which is why the upd protocol was so nice and easy for me to implement in my notification producer server application because it was a simple broadcast message. What is the current relationship between Growl and GfW ? > > I'm working on gathering a list of available resources for gntp, there are > tons of implementations in multiple different languages already. > I'll be interested to see that. > > Keep in mind we're not going to be implementing encryption due to our > concern of violating US export laws. Until we get a clear go ahead on that, > encryption will not be there. > > Chris > > > > >> -- >> You received this message because you are subscribed to the Google Groups >> "Growl Discuss" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/growldiscuss/-/CWo1Zw4FTWoJ. >> >> 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. >> > > -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/growldiscuss/-/5fMaOnRA1sIJ. 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.
