Cloudflare

any ideas about a websocket error 1006 when using the chat demo?

unknown

its doing the TLS handshake and I think thats about it

oh. it had a response body but I didnt even see it

https://github.com/securityheaders/security-headers-cloudflare-worker/issues/8

my issue is related, I get the same error

idk, but I should be allowed to return ``101`` from a worker, but it doesn't let me.

A 101 should work fine as long as you also attach a `webSocket`. Do you have another use-case for 1xx status codes?

What was the issue if you don't mind sharing? It may help others who run into it in future 🙂

well I was passing the request into a sveltekit route to have sveltekit handle it and then return the result (so that all my route handling could be done within sveltekit)

but sveltekit I guess does some kind of stringifying/parsing of the returned value so it was breaking the response object.

it was not an instanceof ``Response`` when it reached the adapter

so instead I just wrote a route directly in the adapter that would intercept specifically websocket requests and deal with them accordingly.

if I use SHA512 to create IDs (hash based on some input), will it "take longer" like it says it does for non-unique IDs

You would have to pass the SHA512 hash into `idFromName()` to get a valid ID. It will have the same performance characteristics `idFromName()` normally has -- so yes, it'll be slower on initial creation than `newUniqueId()`.

one other question that I couldn't see on the docs, is there presently a way to delete a durable object by its ID?

I assume its just ``.delete(id)`` on the namespace, but the documentation didnt mention such a method

I think there’s no way to delete a DO yet….

If you delete the class probably all instances will be deleted, but is just my speculation on that matter.

I am asking about deleting only one instance, not the entire class

Yes I know, I was just saying…. For one instance there’s no way as far I know.

Anyway, someone’s tested the increase latency of a DO call? Here’s is almost 120ms… probably there’s no COLO capable of a DO nearby.