Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Wed, 24 Oct 2007 07:12:05 -0700,    group: microsoft.public.exchange.development        back       


Re: OnSave Store Event Sink: Strange lFlags value    
Can anybody tell me when the EVT_IS_REPLICATED flag is set? I havn't managed 
to provoke it, and still don't understand when this flag is set.

-Knut

"knut" wrote:

> Thank you for the quick answer.
> As I have clearly misunderstood the functionality of EVT_IS_REPLICATED, 
> could you please explain its functionality and differences with EVT_COPY? The 
> short description on msdn (The item is being saved as a result of 
> replication) does not really tell me that much.
> 
> Regards
> Knut
> 
> "Henning Krause [MVP - Exchange]" wrote:
> 
> > Hello,
> > 
> > The EVT_InitNew has nothing to do with the item - it's merely a flag that 
> > indicates that your sink instance has been created.
> > 
> > You should be able to confirm this by adding a log message to the 
> > constructor of the sink class.
> > 
> > Updated items do not have the EVT_NEW_ITEM flag set  - that should give you 
> > enough information.
> > 
> > Kind regards,
> > Henning Krause
> > 
> > 
> > 
> > "knut" <knut@newsgroup.nospam> wrote in message 
> > news:594EF478-9339-49EF-B4BA-CAA9E38106AC@microsoft.com...
> > > Hi all,
> > >
> > > I have a Store Event Sink that (to me) returns incomprehensible IFlags 
> > > when
> > > run.
> > > It seems like the flag always have the bits for EVT_INITNEW set, and I 
> > > can't
> > > understand why.
> > >
> > > This is how it looks when I only log the information given in the OnSave
> > > method. Here I created two task (with the same wonderful name), and then
> > > updated the last:
> > >
> > > 16.10.2007 17:04:26: ## Event Sink started ##.
> > > 16.10.2007 17:04:26: lFlag: 66.
> > > 16.10.2007 17:04:26: lFlags set: EVT_IS_COLLECTION EVT_INITNEW .
> > > 16.10.2007 17:04:26:
> > > file://./backofficestorage/erp.nordicsemi.no/MBX/kl/Tasks.
> > > 16.10.2007 17:04:26: ##Event Sink ended.
> > > 16.10.2007 17:04:26: ## Event Sink started ##.
> > > 16.10.2007 17:04:26: lFlag: 65.
> > > 16.10.2007 17:04:26: lFlags set: EVT_NEW_ITEM EVT_INITNEW .
> > > 16.10.2007 17:04:26:
> > > file://./backofficestorage/erp.nordicsemi.no/MBX/kl/Tasks/New Task.EML.
> > > 16.10.2007 17:04:26: ##Event Sink ended.
> > > 16.10.2007 17:04:47: ## Event Sink started ##.
> > > 16.10.2007 17:04:47: lFlag: 66.
> > > 16.10.2007 17:04:47: lFlags set: EVT_IS_COLLECTION EVT_INITNEW .
> > > 16.10.2007 17:04:47:
> > > file://./backofficestorage/erp.nordicsemi.no/MBX/kl/Tasks.
> > > 16.10.2007 17:04:47: ##Event Sink ended.
> > > 16.10.2007 17:04:47: ## Event Sink started ##.
> > > 16.10.2007 17:04:47: lFlag: 65.
> > > 16.10.2007 17:04:47: lFlags set: EVT_NEW_ITEM EVT_INITNEW .
> > > 16.10.2007 17:04:47:
> > > file://./backofficestorage/erp.nordicsemi.no/MBX/kl/Tasks/New Task-2.EML.
> > > 16.10.2007 17:04:47: ##Event Sink ended.
> > > 16.10.2007 17:08:28: ## Event Sink started ##.
> > > 16.10.2007 17:08:28: lFlag: 64.
> > > 16.10.2007 17:08:28: lFlags set: EVT_INITNEW .
> > > 16.10.2007 17:08:28:
> > > file://./backofficestorage/erp.nordicsemi.no/MBX/kl/Tasks/New Task-2.EML.
> > > 16.10.2007 17:08:28: ##Event Sink ended.
> > >
> > > What I'm after is to only handle items that are updated, and thought
> > > EVT_REPLICATED_ITEM would be correct. However, the only flag set when I
> > > update elements are the EVT_INITNEW.
> > >
> > > Does anybody have a good explenation for this behaviour? 
> > 
> >
date: Wed, 24 Oct 2007 07:12:05 -0700   author:   knut am

Re: OnSave Store Event Sink: Strange lFlags value    
Hello Knut,

I would guess that this flag is set on two circumstances:

1. An event sink is registered on a public folder and an item is being 
replicated from another public folder server
2. An event sink is registered on a mailbox folder and an item is being 
replicated to the mailbox via ActiveSync.

But I'm not sure on this...

Kind regards,
Henning Krause

"knut" <knut@newsgroup.nospam> wrote in message 
news:A49FDCFB-FC42-4C22-8993-52A7315B0B1E@microsoft.com...
> Can anybody tell me when the EVT_IS_REPLICATED flag is set? I havn't 
> managed
> to provoke it, and still don't understand when this flag is set.
>
> -Knut
>
> "knut" wrote:
>
>> Thank you for the quick answer.
>> As I have clearly misunderstood the functionality of EVT_IS_REPLICATED,
>> could you please explain its functionality and differences with EVT_COPY? 
>> The
>> short description on msdn (The item is being saved as a result of
>> replication) does not really tell me that much.
>>
>> Regards
>> Knut
>>
>> "Henning Krause [MVP - Exchange]" wrote:
>>
>> > Hello,
>> >
>> > The EVT_InitNew has nothing to do with the item - it's merely a flag 
>> > that
>> > indicates that your sink instance has been created.
>> >
>> > You should be able to confirm this by adding a log message to the
>> > constructor of the sink class.
>> >
>> > Updated items do not have the EVT_NEW_ITEM flag set  - that should give 
>> > you
>> > enough information.
>> >
>> > Kind regards,
>> > Henning Krause
>> >
>> >
>> >
>> > "knut" <knut@newsgroup.nospam> wrote in message
>> > news:594EF478-9339-49EF-B4BA-CAA9E38106AC@microsoft.com...
>> > > Hi all,
>> > >
>> > > I have a Store Event Sink that (to me) returns incomprehensible 
>> > > IFlags
>> > > when
>> > > run.
>> > > It seems like the flag always have the bits for EVT_INITNEW set, and 
>> > > I
>> > > can't
>> > > understand why.
>> > >
>> > > This is how it looks when I only log the information given in the 
>> > > OnSave
>> > > method. Here I created two task (with the same wonderful name), and 
>> > > then
>> > > updated the last:
>> > >
>> > > 16.10.2007 17:04:26: ## Event Sink started ##.
>> > > 16.10.2007 17:04:26: lFlag: 66.
>> > > 16.10.2007 17:04:26: lFlags set: EVT_IS_COLLECTION EVT_INITNEW .
>> > > 16.10.2007 17:04:26:
>> > > file://./backofficestorage/erp.nordicsemi.no/MBX/kl/Tasks.
>> > > 16.10.2007 17:04:26: ##Event Sink ended.
>> > > 16.10.2007 17:04:26: ## Event Sink started ##.
>> > > 16.10.2007 17:04:26: lFlag: 65.
>> > > 16.10.2007 17:04:26: lFlags set: EVT_NEW_ITEM EVT_INITNEW .
>> > > 16.10.2007 17:04:26:
>> > > file://./backofficestorage/erp.nordicsemi.no/MBX/kl/Tasks/New 
>> > > Task.EML.
>> > > 16.10.2007 17:04:26: ##Event Sink ended.
>> > > 16.10.2007 17:04:47: ## Event Sink started ##.
>> > > 16.10.2007 17:04:47: lFlag: 66.
>> > > 16.10.2007 17:04:47: lFlags set: EVT_IS_COLLECTION EVT_INITNEW .
>> > > 16.10.2007 17:04:47:
>> > > file://./backofficestorage/erp.nordicsemi.no/MBX/kl/Tasks.
>> > > 16.10.2007 17:04:47: ##Event Sink ended.
>> > > 16.10.2007 17:04:47: ## Event Sink started ##.
>> > > 16.10.2007 17:04:47: lFlag: 65.
>> > > 16.10.2007 17:04:47: lFlags set: EVT_NEW_ITEM EVT_INITNEW .
>> > > 16.10.2007 17:04:47:
>> > > file://./backofficestorage/erp.nordicsemi.no/MBX/kl/Tasks/New 
>> > > Task-2.EML.
>> > > 16.10.2007 17:04:47: ##Event Sink ended.
>> > > 16.10.2007 17:08:28: ## Event Sink started ##.
>> > > 16.10.2007 17:08:28: lFlag: 64.
>> > > 16.10.2007 17:08:28: lFlags set: EVT_INITNEW .
>> > > 16.10.2007 17:08:28:
>> > > file://./backofficestorage/erp.nordicsemi.no/MBX/kl/Tasks/New 
>> > > Task-2.EML.
>> > > 16.10.2007 17:08:28: ##Event Sink ended.
>> > >
>> > > What I'm after is to only handle items that are updated, and thought
>> > > EVT_REPLICATED_ITEM would be correct. However, the only flag set when 
>> > > I
>> > > update elements are the EVT_INITNEW.
>> > >
>> > > Does anybody have a good explenation for this behaviour?
>> >
>> >
date: Wed, 24 Oct 2007 18:13:59 +0200   author:   Henning Krause [MVP - Exchange]

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us