Very strange. I sent this: Application-Name: My App Notification-Name: Upload complete Notification-ID: 36fea570ccfa5d5bc27c5e20202b38d7 Notification-Title: Upload complete Notification-Text: First text
Reponse: GNTP/1.0 -OK NONE Response-Action: NOTIFY Notification-ID: 36fea570ccfa5d5bc27c5e20202b38d7 Then a second later: Application-Name: My App Notification-Name: Upload complete Notification-ID: 94659a14696cea7650f2c504d3c35124 Notification-Title: Upload complete Notification-Text: Second text Notification-Coalescing-ID: 36fea570ccfa5d5bc27c5e20202b38d7 Response: GNTP/1.0 -OK NONE Response-Action: NOTIFY Notification-ID: 94659a14696cea7650f2c504d3c35124 This yields in two separate notifications which for a couple of seconds are visible at the same time. Maybe this should be posted as a bug report instead over att google code? On Nov 23, 10:11 pm, Daniel Siemer <[email protected]> wrote: > This has been working fine for me using the 1.3 framework using GNTP > and Growl.app 1.3.1 (I routinely come back to my framework updated > copy of colloquy and watch it coalesce repeated notes from the > bouncer). Could you give a bit more detail on what you are doing, and > what you are seeing? > > On Nov 23, 11:49 am, betamos <[email protected]> wrote: > > > > > > > > > In 1.3.1 the GNTP header "Notification-Coalescing-ID" seems to be > > ignored. It would be great if it was possible to update previous > > notifications over network. > > Thanks. -- 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.
