Allow clients to determine the difference between create or update on PUT

PUT allows an object to be created (http 201).  This allows REST code to
indicate an object has been created and clients to react to it.

Plan on using this for some oauth / user level interactions in the future.
Hrm - returning a non nil error on success seems wrong.  If we return multiple it has to be in the channel, since we probably want to let the completion be async and that will RTT to the db.

Let me think about it more - wrapping seemed least bad unless we let Status contain an object (which feels wrong in other ways).

> On Oct 15, 2014, at 9:05 PM, Daniel Smith <notifications@github.com> wrote:
> 
> In pkg/apiserver/resthandler.go:
> 
> > @@ -29,6 +29,22 @@ import (
> >  	"github.com/golang/glog"
> >  )
> >  
> > +// createOrUpdate may be returned by a handler to distingush between a PUT
> > +// that creates an object and a PUT that updates an object.
> > +type createOrUpdate struct {
> Eek. Multiple return parameters, please! Or hide this in a custom error type!
> 
> —
> Reply to this email directly or view it on GitHub.