Context
Right now, on each IceBreaker connection, we generate a new random UUID API prefix with Uuid::new_v4():
|
// Build a prefix |
|
let api_prefix = ApiPrefix(config.icebreakers_config.as_ref().map(|_| Uuid::new_v4())); |
That prefix changing can introduce some mini-downtimes on the iceproxy1, see e.g. here:
Perhaps it would make sense to generate it once, save in some cache file, and then reuse on subsequent connections and process runs. If the user wants to change it for whatever reason, they still can, but then they cause the mini-downtime.
See also https://github.com/blockfrost/blockfrost-ops/issues/2200#issuecomment-3738692431.
Once everything is running through WebSockets, it's worth thinking whether we need that random prefix at all.
Context
Right now, on each IceBreaker connection, we generate a new random UUID API prefix with
Uuid::new_v4():blockfrost-platform/src/server.rs
Lines 57 to 58 in f3b73de
That prefix changing can introduce some mini-downtimes on the
iceproxy1, see e.g. here:Perhaps it would make sense to generate it once, save in some cache file, and then reuse on subsequent connections and process runs. If the user wants to change it for whatever reason, they still can, but then they cause the mini-downtime.
See also https://github.com/blockfrost/blockfrost-ops/issues/2200#issuecomment-3738692431.
Once everything is running through WebSockets, it's worth thinking whether we need that random prefix at all.