Description

DavideAllavena

opened on Feb 28, 2018

Issue body actions

With this toy example i get no notification when inserting or deleting resources on http://solidtest.space:

const WebSocket = require('ws');
var ws = new WebSocket('wss://davide.solidtest.space/public/twee-fi/');

ws.on('open', function open() {
  console.log('Done');
});

ws.on('message', function incoming(data) {
  console.log(data)
});

The request:

curl -XPUT -H "Content-Type: text/turtle" -H'Cookie:somecookie' 'https://davide.solidtest.space/public/twee-fi/test.ttl' -d "<http://subje.ct> <https://predica.te> <http://obje.ct> .\n"

Reacted by Melvin Carvalho

Activity

1. melvincarvalho

   added

   bug

   help wanted

   on Feb 28, 2018
2. melvincarvalho commented on Mar 5, 2018

   

   melvincarvalho

   on Mar 5, 2018

   Contributor

   More actions

   See also chatlog

   @DavideAllavena is this a blocker? If so, I suggest we add the priority label to this.
3. melvincarvalho

   added

   priority

   and removed

   priority

   on Mar 5, 2018
4. DavideAllavena commented on Mar 5, 2018

   

   DavideAllavena

   on Mar 5, 2018

   Author

   More actions

   Yes this is a blocker. We are developing an application that creates a web-socket to get notified on changes in a container. We can temporarily create a dirt workaround. But we are willing not to do it.
5. melvincarvalho

   added

   priority

   blocker

   on Mar 5, 2018
6. melvincarvalho commented on Mar 5, 2018

   

   melvincarvalho

   on Mar 5, 2018

   Contributor

   More actions

   @DavideAllavena ok thanks, will try and prioritize this. Or if you manage to work out a patch, we'll get it upstream asap! :)
7. michielbdejong commented on Jan 21, 2019

   

   michielbdejong

   on Jan 21, 2019

   Member

   More actions

   @DavideAllavena Is this still an issue? you should send sub /public/twee-fi/ from your WebSocket client to subscribe it. Example: in one window, type:

    wscat --no-check --connect wss://localhost:8443/
   connected (press CTRL+C to quit)
   > sub /inbox
   < ack /inbox

   Then in another window, type:

   curl -kX  POST  https://localhost:8443/inbox

   You'll see < pub /inbox appear.
8. michielbdejong commented on May 7, 2019

   

   michielbdejong

   on May 7, 2019

   Member

   More actions

   We just found out that it's because you're using PUT instead of POST, see #9

Issue actions