On Tue, 2011-10-18 at 15:58 -0400, Matthew Barnes wrote:
> On Tue, 2011-10-18 at 21:29 +0200, Milan Crha wrote: 
> > I'm currently trying to adapt evo-ews to current git master and this
> > change doesn't make much sense there, at least for me, because on the
> > first look there is used a libsoup for authentications, thus no such
> > auth_loop or any "same basic logic". I've a larger patch for the ews
> > under go, which I will finish tomorrow, I only wanted to let you know
> > about this and I hoped that you'll help with this particular thing.
> You might have to implement authenticate() and authenticate_finish()
> instead of authenticate_sync().
> Cache the password that authenticate() gives you, hand it to libsoup
> when it asks for it, and when libsoup responds with a status code,
> complete the GSimpleAsyncResult you created in authenticate().

Note that this also needs to cope with the case where the password
*becomes* invalid in the middle of an active session. The user should be
prompted for a new password (repeatedly until they get it right), and
then it should work for *all* of mail/cal/ebook access.

And if they hit *cancel* instead of entering a valid password, hopefully
it'll stop asking rather than popping up a dialog every few seconds
until they change to a VT and run 'killall evolution' :)


Attachment: smime.p7s
Description: S/MIME cryptographic signature

evolution-hackers mailing list
To change your list options or unsubscribe, visit ...

Reply via email to