Hi, I think you are right - MS Exchange notifications are really poor regarding providing information about the causing item. So that's why I've added some extensions to the Slide server (information about causing item and user of the event). So my suggestion would be to add subscriptions for each item, as this is the only way to work with exchange notifications. I have not tested yet if exchange can handle thousands of subscription but it should do so. Please share your experience as I'm very interested in this issue as well.
Cheers, Daniel "Slide Developers Mailing List" <[email protected]> schrieb am 12.01.05 17:09:46: > > Hi, > > Daniel Florey schrieb: > > I missed something... The javadocs have been correct; they just didn't > > mention that the poll interval should be specified in milliseconds. > > It might be correct that you have to add the username to repositoryDomain > > when connecting to exchange as you also have to specify in the constructors > > credentials which user is taken to poll for events. This will fail if the > > user has no access to a specific path. > > So finally everything seems to be correct (except the fact that there are > > some mysterious methods in WebdavResource regarding subscriptions). > > >>nl.subscribe("Update", "/Kontakte", 1, 3600, 0, new Subscriber() { > >> public void notify(String uri, Map information) { > >> System.out.println("Event occured"); > >> } > >>}, credentials); > > is it correct that the "information" map provided by the notify sink > is always empty? Only the folder "uri" is delivered, not the URI of > the item that caused the event (probably MS Exchange does not > deliver more information?). > > This makes it very difficult to find the item that caused the event. > > - "Update" and "newmember" event sources can be found by searching the > provided folder for the last modified item. > > - But what about "Delete" event sources - do I have to subscribe for > "Move" events at the "Papierkorb"/Trashcan of the corresponding > user? > > It should be easy for MS Exchange to deliver the information needed > to determine the event source, but it does not seem to do :(. > > An alternative solution would be to subscribe for every single > appointment in all folders. That way I know exactly which appointment > has been deleted/updated, but this means probably severe performance > issues (if MS Exchange does really support thousands of > subscriptions...). > > Am I right that MS Exchange's "poor" event notifications are the > issue here - or am I doing something wrong? > > Regards, > > Martin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
