It would be really nice if CF would publish a list of locations that run DO

hello, is the right channel for R2

sorry nevermind

Good idea!

!remind 10hr add toggle for reverse view https://discord.com/channels/595317990191398933/773219443911819284/1052174431675494400

I will remind you in 10 hours at Dec 13, 2022 at 22:00 UTC

Would be interesting to have a tab where you use the new

locationHint

param to

namespace.get

and see the difference

Is that documented somewhere?

I got the alert from `workers-types`: https://github.com/cloudflare/workers-types/pull/323

Should I just test it once, or test every “region” everywhere?

Probably just once or once per coarse location at first, utility of displaying all of the info would decrease quickly if the logic to map those coarse locations -> colos/colo pools is the same in every edge colo, which I'd bet is the case, altho @brett would know for sure

Yeah each hint is the same in every edge colo currently. Subject to change, I suppose.

That feature also isn't deployed just yet, in a few days.

Good, gives me some time to work on it

Reminder for @User: add toggle for reverse view Set

Any consideration of central North America? DFW and/or ORD coverage would be nice ...

As of right now DFW is part of "wnam" and ORD is part of "enam", but we could support more hints in the future. Maybe a "cnam" makes sense?

my 2 cents would certainly be to support

cnam

... as that's better coverage / performance for overall US coverage

js
let id = OBJECT_NAMESPACE.newUniqueId({jurisdiction: 'eu'})
let stub = OBJECT_NAMESPACE.get(id, {locationHint: 'afr'})

🤔

seems weird that options to specify the location in which a DO is created exist both on the id and on the stub.

I dont really think a central location is that important the ping variance between a central and west or east is so minimal that no one will really notice tbh especially considering its going through the CF network

But also none of the big guys give us central anything so maybe CF should 😛

more options are never bad though, you could always just not use all of them. Personally, I think it would be cool if we could pick with as much precision as possible

Oh interesting GCP actually does have a us-central til

GCP has like a million regions in the US lol

could be useful for US central to be defined so I can exclude it for anything that will be used by more than one person I guess

It is weird. The reason Jurisdictions are only supported in

newUniqueId

is because the Jurisdiction is encoded in the ID itself.

idFromName

actors can't really encode something like a Jurisdiction in the ID -- or at least so far we've decided it would confuse people that

NS.idFromName("foo", {jurisdiction:"eu"})

and

NS.idFromName("foo", {jurisdiction:"bar"})

are (forever) different objects. Another factor is that

locationHint

is more of a dynamic thing, we expect hints could change (just like object locations will in the future), but the underlying object is the same. Again: not true for Jurisdictions, which are a constant fact about the object forever.

Can `locationHint`s be ignored? Like, if I request APAC, but for some reason it is unable to create a DO there, does it throw an error? Create it somewhere else?

As long as the

locationHint

is a valid choice it won't throw an error. This is because it's a hint, and especially important because currently objects don't relocate, and so if you created one in ENAM but then did

locationHint: "apac"

we don't want that to be an error