List view

• Pub Sub functionality

  Pub sub. Postponed: there are number of elements I haven't considered. Security: it is impossible (as far as I see) to make sure somebody who is notified have actually the right to be notified, and see the data he is notified about. Connection pool: since connection have to be left opened, it is important to manage this properly so as to maximise the number of channel that can be listened on and minimises the number of connections. This is ok when all connections share the same session user (in case there is no authentication). It becomes tricky when authentication is in place, because session will be different for every listening channel. This needs to be thought through.

  No due date

  •0/1 issues closed
  0% complete1 open0 closed

• v0.5.0

  Overdue by 9 year(s)

  •

  Due by April 9, 2017

  •0/4 issues closed
  0% complete4 open0 closed