Re: [core] pubsub short-review

[Christian Amsüss <[e-mail]>]

Hello Carsten and pubsub authors,

> Indeed.  However, if it is the normal result of an application state
> that results in an error response, it probably is worth to point that
> out in the definition of the application.
> 
> > * The create-on-publish operation is executed using PUT, which MUST be
> >  idempotent according to RFC7252 Section 5.1. Returning 2.01 Created on
> >  first put and 2.04 Changed on the second put is not exactly
> >  idempotent.
> 
> Idempotency in a REST context is with respect to the state on the
> server, not with respect to the response code.  Trivially, doing a
> DELETE will get you a 2.02 only on the first request and a 4.04 on all
> following ones.

You're right, I missed that – implementors might still appreciate a note
that they could receive a 2.04 even if they just created the topic. In
the same vein, the 4.04 one could get on a DELETE is one of the protocol
error codes that would be worth pointing out.

Best regards
Christian

-- 
This may seem a bit weird, but that's okay, because it is weird.
  -- perldata(1) about perl variables