Ok cool, we're on the same page then.  Correct, it hasn't been developed
yet.  Michael Patterson will be building that endpoint and service call.


On Tue, Jan 14, 2014 at 4:21 PM, hlbraddock <notifications@github.com>wrote:

> In src/main/java/org/cru/crs/api/PermissionResource.java:
>
> > +		Simply.logObject(permission, PermissionResource.class);
> > +		
> > +		if(IdComparer.idsAreNotNullAndDifferent(permissionId, permission.getId())) {
> > +			throw new BadRequestException();
> > +		}
> > +		
> > +		/*above, we've just checked for the case that both are non-null and different, this assures us
> > +		 * that the value in the path is set in the body in case the body is null*/
> > +		permission.setId(permissionId);
> > +		
> > +		updatePermissionProcess.updatePermission(permission, crsLoggedInUser);
> > +		
> > +		return Response.noContent().build();
> > +	}
> > +	
> > +	@DELETE
>
> I think providing semantically meaningful endpoints is primary, and to
> that end, revoking by way of DELETE seems reasonable.
>
> By the way, I don't see a DELETE endpoint on the ConferenceResource.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/CruGlobal/conf-registration-api/pull/114/files#r8876533>
> .
>



-- 
*Ryan Carlson*
Sr Programmer / Analyst
Web and Moblie Development Team
ryan.t.carlson@cru.org