[
https://issues.apache.org/jira/browse/RAVE-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Geer updated RAVE-1046:
-----------------------------
Attachment: People.patch
Well, actually, Friends shouldn't really be tied to Users at all but instead
tied to People. I realize right now they are sub/parent classes but in the
future the hope is to make Person and User completely separate but have a
relationship between them. So let's design the REST APIs appropriately,
regardless of what backend service they talk with now.
I've attached a patch I had been working on for People. I'm not saying it's
correct since I was playing with how to serialize the REST side (prior to
Erin's new plan) but the concepts are what I'd like to see if possible on the
REST Resource structure.
> Create Friend Request API
> -------------------------
>
> Key: RAVE-1046
> URL: https://issues.apache.org/jira/browse/RAVE-1046
> Project: Rave
> Issue Type: Sub-task
> Components: rave-core
> Reporter: Michael Jett
> Attachments: People.patch
>
>
> Create a Friend Request API that operates with the User's API. The
> UserService has a built in method "getFriendRequestsReceived." This needs to
> be tied into the UsersResource class or spun off into a separate class.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
