[occi-wg] Microsoft: "Atom Publishing Protocol (AtomPub) as the future direction"

[Alexis Richardson]

List this is OT but may be of just enough interest to those following
David's emails, that I am going to cc occi-wg.

David,

Check out: http://www.reversehttp.net/reverse-http-spec.html

It's a way to make each node be a server and a client.  Built by one of our lot.

alexis



On Tue, May 12, 2009 at 3:58 PM, M. David Peterson <xmlhacker at gmail.com> wrote:
> On Tue, May 12, 2009 at 7:57 AM, M. David Peterson <xmlhacker at gmail.com>
> wrote:
>>
>> The browser vendors need to catch up with the rest of the devices and
>> applications out there which speak fluent HTTP 1.1
>
> I should clarify this statement: From an internal perspective, very few web
> browsers don't speak fluent HTTP 1.1.  They may each interpret the spec just
> a tad bit differently, and they've certainly been known to leave out support
> for critical pieces such as -- oh, I don't know, ETags for example! ;-)
>
> Where they fall short is exposing that support at the API level in a
> consistent, cross browser manner.
>
> This is just my own opinion, of course, but if the HTML5 WG /REALLY/ wanted
> to make a difference they'd stop trying to agree upon defining element names
> and definitions which can just as easily be implemented via the
> 'object/@type' element/attribute combination** , and instead use their time
> to first, come to terms with how to expose full client/server support for
> the HTTP 1.1 spec to the developer such that each node on the net is both a
> client /AND/ a server, to then establish a formalized process for
> introducing additional protocols into the mix that have proven to be of
> value to a broader swath of developers (XMPP anyone? BitTorrent? AtomPub?
> Kermit? ;-)) and are therefore candidates for finding their way into the
> toolbags of /ALL/ developers and usable by /ALL/ folks who just so happen to
> have a communication protocol standards compliant web browser installed on
> their machine.
>
>  A man can dream, can't he! ;-)
>
> ** okay, that's obviously a stretch, but what's the difference between
> agreeing upon a common set of param/@name child elements and defining
> attribute names for a 'video' element? Answer: One less element to have to
> kill off in 10 years when holograms become all the rage and the video
> element goes the way of the blink element. ;-)
> --
> /M:D
>
> M. David Peterson
> Co-Founder & Chief Architect, 3rd&Urban, LLC
> Email: m.david at 3rdandUrban.com | m.david at amp.fm
> Mobile: (206) 999-0588
> http://3rdandUrban.com | http://amp.fm |
> http://broadcast.oreilly.com/m-david-peterson/
>