[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 would be to reverse the client/server roles of the
 previous option.

 Pros:
 * The need for authentication is probably eliminated.  A consumer listens
 on an address and then tells Tahoe-LAFS that address.  The OS enforces
 single listener (there are flags to monkey with this; don't use them).
 * TCP clients like this aren't quite as easy as TCP servers but at least
 the implementation only needs to be in Tahoe-LAFS
 * It's easy to pass the TCP port number in to Tahoe-LAFS from another
 piece of automation.

 Cons:
 * It only enables a single consumer per Tahoe-LAFS process (unless you
 extend it to stream logs to multiple servers...)

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