older frameworks made use of an api called Distributed Notification Center to send the click callback messages to growl. The reason that this no longer functions is because under the sandboxing model you can send notifications to the distributed notification center but you can't supply any contextual information along with it. That contextual information is what an application would set on a given notification when sending it to growl so that when it got a click notification back it would know which notification was clicked, since its possible to have many in-flight notifications at the same time it needs some context for knowing which one it should present to the user.
What we're looking into fixing after Growl 2.1 ships is that the current model for talking to growl is a single transaction, the application sends growl a message, growl keeps the connection open for a period of time and then closes it if there isn't any user feedback. we ended up timing out the connections because what was happening for certain uses is they would end up with a large number of connections remaining open (large enough that it resulted in Growl hitting the per-application open file limit and resulting in cpu spike the next time the CoreData-backed history database tried to write out its data). My proposed solution for post-2.1 is that the application's Growl xpc has a local port it listens on for click callback events. this isn't entirely GNTP compatible, but it makes the transactions much simpler, Application sends Growl a message, connection closes, Growl displays the notification. User clicks notification, Growl opens a connection to the App and says "user clicked on notification with this id", the application would then process that request. Neither would have an open connection for long and the max open files, click callbacks, and coredata all would function as intended. -rudy On Thursday, November 15, 2012 3:23:54 AM UTC-5, DataGreed wrote: > > I really don't get it. Why can't it handle clicks from older frameworks? > > среда, 14 ноября 2012 г., 18:49:41 UTC+4 пользователь Christopher Forsythe > написал: >> >> We do, it's in volume licensing, and it is also sandboxed. So it has the >> same issue with really old frameworks not being able to do the clicking, >> since sandboxing does not allow for NSDNC in the way that we were using it. >> So that wouldn't help here. >> >> Chris >> >> On Wed, Nov 14, 2012 at 4:01 AM, DataGreed <[email protected]> wrote: >> >>> same problem here. Why not release an alternate version of growl (not >>> for appstore) that can handle application links from the older version of >>> framework? >>> >>> воскресенье, 23 сентября 2012 г., 7:21:53 UTC+4 пользователь Sulaiman >>> написал: >>> >>>> Hi, >>>> >>>> I have just recently updated the Growl to 2.0 and i'm having issue with >>>> Growl using Mountain Lion and i have noticed that when i clicked the >>>> notification (when email arrived in Sparrow and clicked it should redirect >>>> to the app behavior in 1.4) it doesn't redirect me to the mail client for >>>> example when someone becomes available and Growl responds and shows up the >>>> notification and when i click that it takes me to the person whom i >>>> clicked, But now it's different when i clicked the notification it doesn't >>>> take me and it just stay on desktop. >>>> >>>> I would like to go back to Growl 1.4 it's better and works perfectly >>>> and how can i get back? >>>> >>>> >>>> Please let me know and its more importance to me as i have been working >>>> on several tasks and only Growl helps me to remind (Likes of Reminder, >>>> Task >>>> complete, Milestones) of those works! >>>> >>>> Thanks, >>>> S. >>>> >>> -- >>> 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/-/SUdFLgqsw0YJ. >>> >>> 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. >>> >> >> >> >> -- >> Chris Forsythe >> @The_Tick <http://twitter.com/The_Tick> >> >> -- 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/-/ZjFcvxnrMCEJ. 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.
