Does anyone have numbers on roundtrip time to Durable Objects living on the other side of the world?
Does anyone have numbers on roundtrip time to Durable Objects living on the other side of the world?
idFromString() specifically parses the output of id.toString(). It won't work with any string that wasn't specifically created by stringifying an ID from the same namespace. idFromName() takes any string you want and returns a unique ID corresponding to it.idFromHex() US https://croquet.io/cloudflare/?EDHEob1TnShyWTdrRoe-GCIdl4E9x7Zz6qqJg7WFnpSJPhttps://croquet.io/cloudflare/?3honQOd0yTj4F0-2-oaIFpP4D4n4S-9S3joiVfLY4nmEUhttps://croquet.io/cloudflare/?ihlwFIj1Z9-BtUfoNAEzD0ItTEZl1qsZrpR8n_BNx2Von fibre at homeI "only" have 1000/500 over COAX (DOCSIS 3.1) :/
1.1.1.1 (on VPN to M247 in Amsterdam) gives me a latency of 28 ms, so perhaps the route between AMS and FRA is just slow for some reason?stub.fetch(request)https://1.1.1.1/cdn-cgi/trace from inside the DO, and cache the colo field from that tracecf property on each incoming fetch request, so request.cf.colo is defined for the incoming worker request, but the Request passed to your DO's fetch still does not have the cf property (I just double-checked) - it makes sense since many of the custom cf properties don't apply for the internal DO fetch calls, but a colo accessor (maybe on state?) would certainly be useful/cdn-cgi/trace > colo=OTP