You cannot post messages because only members can post, and you are not currently a member.
Description:
GetPingd.com
|
|
|
General web hook discovery and registration
|
| |
I'm starting to think about a standard way for web hook event discovery and callback registration. I've kind of known GetPingd does pretty much that, but since I haven't actively been thinking about this, I haven't put them together. I'd be interested in working with you guys to think about this in the context of web hooks in general. The main thing (and maybe why I didn't... more »
|
|
|
typo...
|
| |
"For clients that may be behind firewalls, not have persistent names,
etc, the XMPP subscription method is far more likely to be
appropriate. "
-> "... etc, the HTTP subscription method is far more..."
|
|
|
BarCamp Boston
|
| |
I will be hosting a session at BarCampBoston this Saturday on
Distributed Twitter. If there is anyone on this mailing list in the
Boston, MA area, please come and contribute to the conversation!
[link]
Thx,
Joe Cascio
|
|
|
Initial thoughts/questions...
|
| |
Thanks for doc'ing these thoughts in a spec proposal type format;
really helps crystalize the thinking.
1) this feels primarily like a mechanism to allow user-facing
applications (e.g. an RSS reader-like thing/client-app) to present
"pings"/updates to said end-users. thoughts around machine-to-machine/... more »
|
|
|
introduction
|
| |
I just joined the list so I figured I'd say hi. Let me know if I can help out with the XMPP end of things. :) Peter
|
|
|
subscription request formats
|
| |
guys, just wanted to say once again - really nice work.
uhm.. just a couple of things.
it states very clear: "the subscription method instead aims to be
extensible as per the mechanisms used in many other IETF RFCs", but do
you think it would be wise to recommend some? I mean, if I was a
"regular" developer, I wouldn't really go and implement any possible... more »
|
No more topics in this group.
|
|
