After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 262438 - make operations cancellable
make operations cancellable
Status: RESOLVED WONTFIX
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
1.0.x
Other All
: Normal major
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
gnome[unmaintained]
: 270375 548605 (view as bug list)
Depends on:
Blocks: 327514
 
 
Reported: 2004-08-04 16:12 UTC by Dan Winship
Modified: 2013-07-23 14:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Dan Winship 2004-08-04 16:12:32 UTC
Connector operations need to be cancellable. This means using
E2kOperation correctly everywhere (ebrowse has examples) instead
of just passing NULL.

e-book-backend-exchange.c already has some support; the "ops"
hashtable. stop_book_view and cancel_operation are already there,
they just don't work because none of the calls actually create
an E2kOperation and stick it in the ops hash table.

e-book-backend-gal.c and the calendar stuff currently has no support,
but it would work similarly to e-b-b-e.

The mailer needs a lot more work to be cancellable, since there's
currently no way for the camel part to tell the backend to cancel
something.
Comment 1 Sushma Rai 2006-01-06 11:05:30 UTC
*** Bug 270375 has been marked as a duplicate of this bug. ***
Comment 2 Sankar P 2006-05-26 12:56:02 UTC
I guess it is similar to some of the work-done by Varadhan
Comment 3 Sushma Rai 2006-05-30 08:51:52 UTC
Not sure which fix you are speaking about, but the bug is about
enabling cancelling operations by pressing "X" mark icon.
Fejj and Partha have fixed this in IMAP and GroupWise providers.
Comment 4 Bharath Acharya 2008-08-22 07:05:58 UTC
*** Bug 548605 has been marked as a duplicate of this bug. ***
Comment 5 Akhil Laddha 2008-08-22 07:36:57 UTC
last dup in 2.23.x 
Comment 6 Milan Crha 2008-12-01 10:53:16 UTC
is this obsolete by evolution-mapi?
Comment 7 André Klapper 2012-09-20 14:49:53 UTC
The "evolution-exchange" package only supports Exchange 2000 and 2003 servers. Newer versions such as Exchange 2007 and 2010 are not supported by "evolution-exchange". It is required to use the package "evolution-ews" (or to some extend "evolution-mapi") for newer version fo Exchange servers.

If the problem/request described in this report still happens with a recent version of "evolution-ews" or "evolution-mapi", please add a comment to this report (and update the "product" setting accordingly if possible).

There are currently no plans to continue the development of the package "evolution-exchange", so this report will soon be closed as WONTFIX.
Thanks for your understanding and sorry that the reported problem was not solved in time in the package "evolution-exchange".
Comment 8 André Klapper 2013-07-23 14:30:03 UTC
evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago.

evolution-exchange is now deprecated and not under active development anymore.

It is unlikely that there will be any further active development.

Closing this report as WONTFIX as part of Bugzilla Housekeeping.

Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.

Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported.
Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.