EldoS | Feel safer!

Software components for data protection, secure storage and transfer

GetOriginatorProcessName return null in WriteCallback Event

Also by EldoS: Solid File System
A virtual file system that offers a feature-rich storage for application documents and data with built-in compression and encryption.
Posted: 11/03/2008 00:43:40
by lcp lcp (Basic support level)
Joined: 10/07/2008
Posts: 17

GetOriginatorProcessName return null in WriteCallback Event
Posted: 11/03/2008 01:11:46
by Eugene Mayevski (Team)

This is correct. GetOriginator* methods should be called only in response to file create and open requests. In those requests you should to obtain originator-related information (if you need it) and store it somewhere and place a reference of some kind to UserContext. Then in other callback handlers analyze information stored in (or referenced by) UserContext. The reason is that some operations can be initiated by system components (cache manager etc) for which GetOriginator* functions return no information. But these operations are performed on files opened by some process, so even if GetOriginator*() return no info, UserContext, which you have set up in create/open callback handler, will be valid.

Sincerely yours
Eugene Mayevski



Topic viewed 4000 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS business operates as a division of /n software, inc. For more information, please read the announcement.

Got it!