[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2844: readiness status API for clients

[Tahoe-LAFS]

#2844: readiness status API for clients
-------------------------+-----------------------
     Reporter:  dawuud   |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  unknown  |    Version:  1.11.0
   Resolution:           |   Keywords:
Launchpad Bug:           |
-------------------------+-----------------------

Comment (by dawuud):

 i don't know much about writing http APIs but i was thinking to write a
 polling http api that outputs JSON and it looks like i could copy a lot of
 code from the magic folder status http api; anyway i wrote this is_ready
 method for Clients to determine if at least k storage servers are
 connected:
 https://github.com/david415/tahoe-lafs/commits/2844.add_readiness_api.0

 maybe this readiness doesn't make sense for storage servers? or would they
 be ready after they have announced themselves to at least one introducer
 or all introducers?

 also, what would it mean for an introducer to be ready? they are always
 ready so perhaps this isn't meaningful for introducers.

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