Skip to content
This repository has been archived by the owner on Apr 13, 2022. It is now read-only.

PubSub #11

Open
elf-pavlik opened this issue May 2, 2015 · 3 comments
Open

PubSub #11

elf-pavlik opened this issue May 2, 2015 · 3 comments

Comments

@elf-pavlik
Copy link
Member

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
Copy link
Contributor

deiu commented May 2, 2015

  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
Copy link
Member Author

  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
Copy link
Contributor

deiu commented May 4, 2015

  1. I agree, SSE looks pretty sweet.

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants