| commit | d44d7efd36073ccee91fb925c42cad4d226da7fd | |
| author | Petr Písař <petr.pisar@atlas.cz> | |
| Fri, 29 Jan 2010 10:37:50 +0000 (29 11:37 +0100) | ||
| committer | Petr Písař <petr.pisar@atlas.cz> | |
| Fri, 29 Jan 2010 10:37:50 +0000 (29 11:37 +0100) | ||
| tree | c97b49ed72fa582a32180c92869feaddac19444f | treesnapshot (tar.gz zip) |
| parent | 98dbe4693895e93c674640ce10ed3c91df21269e | commitdiff |
doc, client: Ajdust how UpdateDataBoxUser works
ISDS apparently does not use old user data only to identify changed user. It
uses these client supplied data to detect differences against new user data
and to authorize these changes.
Thus client must supply complete original old user data. Therefore application
will usually need to duplicate user data. Appropriate functions has been
implemented into library and exported.
ISDS apparently does not use old user data only to identify changed user. It
uses these client supplied data to detect differences against new user data
and to authorize these changes.
Thus client must supply complete original old user data. Therefore application
will usually need to duplicate user data. Appropriate functions has been
implemented into library and exported.
| client/changeuser.c | diffblobblamehistory | |
| doc/maintanance_web_services | diffblobblamehistory |