Opened at 2022-08-08T14:41:41Z
Last modified at 2022-11-16T16:05:40Z
#3912 closed task
Storage server announces HTTP storage protocol with NURLs — at Version 2
| Reported by: | itamarst | Owned by: | itamarst |
|---|---|---|---|
| Priority: | normal | Milestone: | HTTP Storage Protocol |
| Component: | unknown | Version: | n/a |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description (last modified by itamarst)
This is part of #3901. It is blocked by #3902.
Storage nodes send the NURL to an introducer, in addition to the fURL for legacy Foolscap protocol. Code would be allmydata/client.py, _Client.init_storage().
- There are actually multiple NURLs for a server? So we need to send all of them. Probably add anonymous-storage-NURLs field to announcements that contains a list of NURL strings.
- This is sent as an announcement "upgrade" so it supersedes the existing announcement, which won't have NURLs if it's an existing server. Investigating what the real name of this is.
Change History (2)
comment:1 Changed at 2022-08-08T14:57:11Z by itamarst
comment:2 Changed at 2022-08-08T14:57:37Z by itamarst
- Description modified (diff)
Note: See
TracTickets for help on using
tickets.
AFAICT all announcements are upgrades: specifically looking at allmydata/client.py, where Client.init_storage(), which calls publish(), which is presumably the publish() in introducer/client.py, which always increments the sequence number for the message.