Re: [Coapp-developers] Async notification from CoApp Engine (libCoApp)

2010/6/10 Jernej Simončič : > of course, I've yet to see list management software that exposes > this setting to the individual subscriber - not like it's more > important than 20 other settings most mailing lists expose) https://launchpad.net/~launchpad-dev ;) I'm sure we could submit a fix somew

Re: [Coapp-developers] Async notification from CoApp Engine (libCoApp)

Ditto! /rafael On 6/9/2010 2:07 PM, Elizabeth M Smith wrote: > On 6/9/2010 2:05 PM, Philip Allison wrote: >> I'm not Elizabeth, but since there was no reply (at least not that I >> can see), I'll bite. Basically, there are only two (sensible) ways >> to do it: callbacks, or a "get current status

Re: [Coapp-developers] Async notification from CoApp Engine (libCoApp)

On Wednesday, June 9, 2010, 20:25:09, Olaf van der Spek wrote: > Don't you love the lack of a reply-to header? ;) That's why there are e-mail clients that fix that for you :) (some people seem to be allergic to Reply-to which defaults to mailing list; of course, I've yet to see list management s

Re: [Coapp-developers] Async notification from CoApp Engine (libCoApp)

are you use better on Windows. -Original Message- From: Olaf van der Spek [mailto:olafvds...@gmail.com] Sent: Wednesday, June 09, 2010 11:25 AM To: Garrett Serack Cc: Philip Allison; coapp-developers@lists.launchpad.net Subject: Re: [Coapp-developers] Async notification from CoApp Engine (

Re: [Coapp-developers] Async notification from CoApp Engine (libCoApp)

On Wed, Jun 9, 2010 at 8:08 PM, Garrett Serack wrote: > Ah, she did reply but to me directly: Don't you love the lack of a reply-to header? ;) Olaf ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpa

Re: [Coapp-developers] Async notification from CoApp Engine (libCoApp)

Garrett Serack Cc: coapp-developers@lists.launchpad.net Subject: Re: [Coapp-developers] Async notification from CoApp Engine (libCoApp) I'm not Elizabeth, but since there was no reply (at least not that I can see), I'll bite. Basically, there are only two (sensible) ways to do it: c

Re: [Coapp-developers] Async notification from CoApp Engine (libCoApp)

On 6/9/2010 2:05 PM, Philip Allison wrote: I'm not Elizabeth, but since there was no reply (at least not that I can see), I'll bite. Basically, there are only two (sensible) ways to do it: callbacks, or a "get current status" function. The former is very common, but does require a bit of thre

Re: [Coapp-developers] Async notification from CoApp Engine (libCoApp)

I'm not Elizabeth, but since there was no reply (at least not that I can see), I'll bite. Basically, there are only two (sensible) ways to do it: callbacks, or a "get current status" function. The former is very common, but does require a bit of thread safety awareness in the app's callback imple

[Coapp-developers] Async notification from CoApp Engine (libCoApp)

Hey Elizabeth, What's your plan for async notification for current status, progress, etc from the engine API? Callbacks? G [Description: Description: fearthecowboy] Garrett Serack | Microsoft's Open Source Software Developer | Microsoft Corporation Office:(425)706-7