Another question about IndexTrigger

[Karl �ie]

Hi again. Just wondering why the IndexTrigger triggers the update event 
before the create event? If a resource is replaced with a new version 
only the update event is sent, so i just thought the order of the 
events looked a bit strange.

Can anybody tell me why the order of the events are "update,create, 
delete" instead of "create, update, delete"? Just wondering because 
when implementing the Index interface i must perform some checks about 
if im doing a create on a already created index or a update on a index 
that has not yet been created. No critic here, jsut want to know.

Mvh Karl �ie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]