I don't know why a sync notification would occur as a result of the backup
conduit backing up a database. The only exception to the rules I point out below
is that a SyncReadPositionXMap() Sync Manager call in a conduit will cause the
sync notification to occur. The backup conduit does not issue this call.
-Geoff Richmond
Palm Computing Developer Support
Shannon <[EMAIL PROTECTED]> on 10/29/99 08:40:44 AM
Please respond to [EMAIL PROTECTED]
Sent by: Shannon <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (Geoff Richmond/HQ/3Com)
Subject: Re: Sync Notification Order
I have seen cases where the backup conduit has caused a sync
noitification launch code to be sent. Is it the case that any
database that has the backup bit set will get the launch code?
Shannon
> > 1) Does the sysAppLaunchCmdSyncNotify launch code get sent to an
> > application immediately after its conduit is done, or is it broadcast
> > to all apps after all the conduits are done synchronizing?
>
>The sysAppLaunchCmdSyncNotify launch codes get sent after all
>conduits are done
>synchronizing.
>
> > 2) Are there any specific rules that the OS follows in order to
> > determine whether to send the code to a particular app, or do all the
> > apps get it?
>
>At the end of a HotSync(R) session, a list of creator id's is generated
>containing all creator id's of databases that were modified during the sync
>operation. Then, each corresponding app for each entry in the list of creator
>id's is sent the launch code. A database is considered modified if the
>modification number in the database header (see modNumP parameter in
>DmDatabaseInfo() documentation) is changed during the sync session.
>
>-Geoff Richmond
>Palm Computing Developer Support
