search

solid / solid-spec

Solid specification draft 0.7.0
Creative Commons Zero v1.0 Universal
1.13k stars 103 forks source link

PubSub #11

Open elf-pavlik opened 9 years ago

elf-pavlik commented 9 years ago

Background

HTTP/1.1 200 OK
...
Updates-Via: wss://example.org/
sub https://example.org/data/test
pub https://example.org/data/test

Questions

1) Any plans to support Server-Sent Events besides Websockets? I understand that client just subscribes and doesn't send any data to server. 2) Could client receive 'fat pings' including payload, for example patch for the resource with optional checksum for checking integrity.

seeAlso

deiu commented 9 years ago
  1. Sure, if we ever find the time to implement it, or if someone wants to submit a PR to our servers. But I don't think we'll mandate it for now.
  2. Yes, we're currently looking into it. We'll probably use LD Patch for it.
elf-pavlik commented 9 years ago
  1. If you only use Updates-Via to receive updates. It may make sense to mandate SSE instead of Websockets. I must admit that I didn't even try setting up wss: yet, but thought of simply using same https: as in other requests, sounds attractive to avoid need to deal with setting up extra TLS certificates.
  2. Currently Social WG charter says JSON (possibly JSON-LD). Some people might prefer JSON Patch over LD Patch. Would LD Patch have also JSON-LD serialization? http://opencreds.org/specs/source/identity-credentials/#writing-data-to-the-identity https://lists.w3.org/Archives/Public/public-linked-json/2015Apr/0000.html
deiu commented 9 years ago

1) I agree, SSE looks pretty sweet.

2) I doubt it will ever serialize to JSON-LD.