On Thu, 2014-11-20 at 17:26 +0000, Schaufler, Casey wrote: > > We could get a simpler interface if the file would be created already in the > > final destination, at user's home directory. > > I'mthinking about a security-manager API that would implement creation of > > an empty file in the user's home directory and pass the file descriptor to > > the > > caller. The caller (e.g. obexd) would then write to that file descriptor to > > fill it > > with data. Things that security-manager should do in such case: > > - take target user name, file name and type as argument > > - verify privilege, can also trigger popup to get user consent > > - check if the file already exists, guard against overwriting it (either by > > failing > > orappending some string to the file name) > > - create the empty file, set ownership and Smack label > > - send the file descriptor back > > In another thread someone explicitly wanted to create the file > in the service's private place and only pass it to the user when > the file was complete.
That depends on the usage. The API needs to support both. The use case for reading files immediately is PBAP transfers where SyncEvolution already starts processing the incoming contacts while obexd is still receiving data and writing into the file. That makes the entire operation (transfer + processing) finish faster. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
