Callback? Callback-Location?

[Jeff Lindsay]

Anybody have thoughts on this?

http://tools.ietf.org/html/rfc6648

Pointed out to me by @johnsheehan. More of this thoughts:

http://john-sheehan.com/post/36704862225/x-callback-header-evented-web-building-block-by

--
Jeff Lindsay
http://progrium.com

[Matthew Hudson]

RFC excerpt:  

SHOULD assume that all parameters they create might become standardized, public, commonly deployed, or usable across multiple implementations.

Looks like they're encouraging you to swing for the fences.

As for the precise header name, Callback-Location seems solid. I'm trying to think of any other services that accept URLs in their headers and coming up blank. Might be helpful to see some other naming conventions.

--
You received this message because you are subscribed to the Google Groups "WebHooks" group.
To post to this group, send email to webh...@googlegroups.com.
To unsubscribe from this group, send email to webhooks+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/webhooks?hl=en.

--

V/R

Matthew Hudson

Website | Blog | Facebook | Google+ | Twitter

[Jeff Lindsay]

The problem I have with Callback-Location is that it's more than a location, it's also parameters. I think of it like a data structure. The Link header, which X-Callback is based on, is a format for defining a Link. And a Link is more than a URL. A URL is a URL, but a Link represents a connection between URLs. That's why you have parameters rel, rev, etc. Because those are important attributes of a Link.

Because the existing Location header (and Content-Location header) have set a precedence of being about just a URL, I would probably avoid using "Location" in the name for this. 

Off the top of my head, I can only imagine two suitable names: Callback or Callback-Link

-jeff

Jeff Lindsay
http://progrium.com

[Timothy Fitz]

Just thinking the same thing. What about "Callback-Webhook" ? :)

Dreaming of a world where we can do this:

Callback-Webhook: <http://example.com/endpoint>; content-type=application/json 

[Jeff Lindsay]

I hate "webhooks". Haha...

How about Webback-Callhook.