[Dev] Sharing invitation sending asyncness

[Bryan Stearns]

Brian and I talked about this a bit today; some of the special-case-ness 
of our current invitations is going to go away, which will allow the 
existing success/failure callbacks to be used for invitations.

We can certainly revisit this when we have a need to use other 
transports, but for now, this seems like a good simplification to our 
existing code.
...Bryan

Morgen Sagen wrote:

> I agree the email layer shouldn't really have to know anything special 
> about sending invitations, especially now that it doesn't need to 
> detect inbound invites -- in fact, perhaps someday invitations could 
> also be transmitted by other means, IM, etc.
>
> On Feb 7, 2005, at 11:24 AM, Bryan Stearns wrote:
>
>> Brian,
>>
>> Currently, when we send sharing invitations, the messages are sent 
>> asynchronously; the sharing code doesn't have a way of finding out 
>> whether the sending was successful (and therefore, no way to help the 
>> user adjust to a mailing or addressing failure).
>>
>> I'm thinking that the sharing-invitation generation stuff should move 
>> into the UI layer: the UI layer (specifically, 
>> MainView.onShareItemEvent, or something factored out from it) would 
>> create the message objects, initiate sending, wait for sending to 
>> complete or fail, then examine the message to check success. What do 
>> you think?
>>
>> ...Bryan
>>
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>
>> Open Source Applications Foundation "Dev" mailing list
>> http://lists.osafoundation.org/mailman/listinfo/dev
>
>
>