Emits websockets-pubsub on the parent containers

[michielbdejong]

When a parent container changes, it's not picked up by https://github.com/solid/node-solid-ws/blob/master/index.js because that code only looks at the URL of the request and has no way of knowing whether any parent containers were created in the process. We probably need to call https://github.com/solid/node-solid-server/blob/0542fa24b240936eac3a8051f9ca01a8e93e1912/lib/create-server.js#L103 explicitly when adding/removing entries in (parent) containers

[jaxoncreed]

I'm having this problem too. I might devote some time to fixing it.

[RubenVerborgh]

I was talking to @timbl about this yesterday in the context of https://github.com/solid/community-server/pull/339

Given a resource R and a container C.

Out of that discussion came:

• upon PATCH to R: pub R
• upon PUT to R: pub R
• upon DELETE to R: pub C, pub R
• upon POST to C, pub C, pub R' (where R' is the newly created resource)

The Community Solid Server will implement the above.

[jaxoncreed]

I will work on updating NSS to do the above.