[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3006: Expose the Eliot logs in a safer way

[Tahoe-LAFS]

#3006: Expose the Eliot logs in a safer way
-------------------------+-----------------------
     Reporter:  exarkun  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  unknown  |    Version:  1.12.1
   Resolution:           |   Keywords:
Launchpad Bug:           |
-------------------------+-----------------------

Comment (by exarkun):

 Another possibility is to extend the existing http-based status interface
 to expose this information.  There are probably many flavors of this
 general idea.  There could be a resource you poll, a resource you "long
 poll", server-sent events (sse), WebSockets, etc.

 For any of these http-based interfaces, authentication is required - eg
 with `api_auth_token`.

 Pros:
 * Ask anyone: the web has won.
 * Supports multiple consumers.
 * Comes with built-in versioning to support future changes (new behavior?
 new url.)
 * Autobahn should make this easy.

 Maybe-Pros:
 * Comes with straightforward TLS for confidentiality (but do you ever
 actually want to expose this to non-localhost?)
 * Other WebSocket features like compression and framing

 Non-Cons:
 * Tahoe-LAFS already transitively depends on Autobahn via magic-wormhole

 Cons:
 * High complexity (software involved, concepts involved, computational &
 memory requirements) option

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3006#comment:4>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage