Page Comparison

...

NAU responses

1. user/pass in https is what we usesufficient, but pluggable would be nice.
2. ?
3. REST is fine.
4. Not necessary.
5. It depends on the kind of call. In a user interface, add/mod/delete of groups is usually one at a time, so can be simple. Member management is usually many at a time so should be batched. Not sure what is meant by "can you pass a TX".
6. Complex. Maybe an option to return simple or complex info on per call basis.
7. Prefer errors and warnings with code and description. Success can be a simple code.
8. It is a success, but there should be info returned to reflect the difference (i.e different result code from success, not already a member). The more granular the return info is, the better. The user can decide whether the difference is relevant to their application.
9. Paging not necessary as part of the interface. Paging needs seem very application-specific. Sorting not necessary, but would be nice if sort field can be specified (e.g. group id vs group name vs other group attribute).
10. Don't have a need for it now.
11. Yes, but result code should reflect any differences per 8.

...