Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

View file
nameuse-case-e.pdf
height250

Use case F - Tracking request and acceptance counts

Flow Diagram

Discussion about the rationale behind some design decisions

...

Alternative implementations


DescriptionProsCons
1

POST /emailInvitation and POST /tokenMembershipInvitation

(Proposal described above)

+ Supports most use cases (all but B)

+ Simple -> less development time

- Not RESTful
2

Same as option 1, but store EmailInvitation in the database and implement REST methods for it.

I.e. GET /emailInvitation, GET /emailInvitation/{id}, DELETE /emailInvitation/{id}, etc.

+ Supports use case B

+ RESTful

- More complex -> more development time
3

User precursor

+ Supports use case B

+ More easily extensible (future support for operations other than inviting to a team)

+ RESTful

- Even more complex -> more development time

- ACL management is out of scope