Can we see the mojo?

[Lachlan Hardy]

G'day Chris et al!

I was wondering when we can see the sexiness of SyncStream. And if it's not sexy yet, can we see what you've got?

Sounds very interesting and I'd love to see what I can do to help make it a reality.

Thanks!

Lachlan

[Lachlan Hardy]

G'day folks

Just figured I'd put this out there again.

Is there any material we can see yet? Code, documentation, whatever?

Thanks!

Lachlan

[Paul Jones]

Hi Lachlan,

A good place to look would be over at the GetPingd group - a lot of the magic about SyncStream (such as notifications) is being discussed in the context of the GetPingd protocol.

Paul.

[Lachlan Hardy]

Hi Paul!

A good place to look would be over at the GetPingd group - a lot of the magic about SyncStream (such as notifications) is being discussed in the context of the GetPingd protocol.

I've been following the group. I think I'm confused by some of the jargon there as, although Syncstream is referred to as an 'implementation' of GetPingd, you've also stated that 'nothing is implemented for real yet'. So I thought I'd come over here to see what's what.

GetPingd is also referred to as both service and a protocol. I find those terms to mean two things quite different, so if you could clarify, I'd be grateful.

Basically, I'm looking to discover the state of play of Syncstream and GetPingd. From the Techcrunch post, I understood that Syncstream was functional. Not ready for the prime time or anything, but active and present.

As for GetPingd, I'm now curious as to the relationship to Syncstream and what its status is as a project. Is it a spec for a service or a protocol? Who owns that spec? What license is the work under?

I don't necessarily expect that you have those answers yet, but even some statements of intention and ownership around that would be a good start

Thanks!

Lachlan Hardy

[Paul Jones]

Hi Lachlan,

Sorry for the delay in replying, it has just been one of those weeks.

On Wed, May 14, 2008 at 8:40 AM, Lachlan Hardy <lachla...@gmail.com> wrote:

Hi Paul!

A good place to look would be over at the GetPingd group - a lot of the magic about SyncStream (such as notifications) is being discussed in the context of the GetPingd protocol.

I've been following the group. I think I'm confused by some of the jargon there as, although Syncstream is referred to as an 'implementation' of GetPingd, you've also stated that 'nothing is implemented for real yet'. So I thought I'd come over here to see what's what.

SyncStream is Faraday's implementation of GetPingd and many other RESTful style ideas. It isn't quite ready for release yet.
 

GetPingd is also referred to as both service and a protocol. I find those terms to mean two things quite different, so if you could clarify, I'd be grateful.

GetPingd is a "service" that can be provided by a given site/resource that speaks a "protocol" defined in the GetPingd specification. If you wanted to clean up the terms, then you could theoretically say that GetPingd is purely a protocol, and resources must provide a subscription service (which happens to speak the GetPingd protocol).
 

Basically, I'm looking to discover the state of play of Syncstream and GetPingd. From the Techcrunch post, I understood that Syncstream was functional. Not ready for the prime time or anything, but active and present.

As for GetPingd, I'm now curious as to the relationship to Syncstream and what its status is as a project. Is it a spec for a service or a protocol? Who owns that spec? What license is the work under?

I guess as I stated above, GetPingd is a specification for a protocol. The specification is currently authored by Faraday Media, but we believe it is in everyone's interest for many other implementations to appears, as it can provide some quite fascinating features to the web. And anyone else is certainly welcome to help write the specification too.
 
Paul.

[Lachlan Hardy]

I guess as I stated above, GetPingd is a specification for a protocol. The specification is currently authored by Faraday Media, but we believe it is in everyone's interest for many other implementations to appears, as it can provide some quite fascinating features to the web. And anyone else is certainly welcome to help write the specification too.

Okay. Thanks, Paul!

Lachlan