@Ashley unfortunately cron is not an option for me. it needs to execute on demand.
@Ashley unfortunately cron is not an option for me. it needs to execute on demand.
DThere's some use cases that just aren't going to be a good fit for the (current) Cloudflare offerings. This might be something you have to do on another compute platform.
DI've been moving various things from AWS to CF myself, but some things are staying at AWS (for now) due to their requirements just being a better fit for AWS solutions.
HVia a WebSocket?
HAt least afaik returning a Reaponse while still receiving a Request is against the HTTP Spec
HMaybe, though it isn’t guaranteed
HFor billing reasons?
Etrying to profile my worker locally and i only see (program) no details, am i missign smth?
HOh nvm, I just read the progress part. Yeah, an XHR is probably the easiest
HBasically, when you make two requests in quick succession from the same browser(and device), it usually hits the same Worker instance
IIf this is regarding your comment the other day about tracking progress of uploads, you don't need the server to respond with the progress.
IYou can just upload using multiple chunks on the client, and then update the progress once each chunk is done (without the server sending back some sort of progress indicator).
Emb issue was solved very recently updated and its fine
IFor example, if you have a 100mb file, upload in 5MB chunks, and each chunk that was successful, increment the progress by 5%.
IYou can still use XHR. Just rather than making 1 big request of 100MB, you make 20 little requests of 5MB each.
IAnd then when the first request is done, you set the progress to 5%, then when the second one is done, the progress is 10%, etc.
ICorrect, yes. That's another reason using small chunks is helpful.
IYou can make as many smaller requests as you want without being limited.
IYou need to use a server regardless (unless you used signed URLs).
IThe method I was suggesting was just to track the progress on the client.
IYou don't need the server to somehow reply and tell you the upload progress, the client already knows because it's the one doing the upload.
Bquick question about using a cloudflare worker for hosting metadata and getting an error loading images. if there are any devs in here or someone can point me in the right direction i would appreciate it.
AIf I call a service binding worker several times in a worker, each call can make 50 subrequests or they can only make 50 in total?
Sdoes anyone have an idea with disabling cache for certain endpoints for my cf workers hono-based server?
The issue is, i am using a KV storage to track the number of items are in processing stage for any user. and from frontend - there is a process counter api which returns the number of items in processing. (called at an interval of 2 seconds.)
When an process is complete - the number is update in kv storage. if I call the api from somewhere else like let's say postman or terminal using curl - the response is up to date number.
but for browser it takes like 10 more seconds to get that updated number.
The issue is, i am using a KV storage to track the number of items are in processing stage for any user. and from frontend - there is a process counter api which returns the number of items in processing. (called at an interval of 2 seconds.)
When an process is complete - the number is update in kv storage. if I call the api from somewhere else like let's say postman or terminal using curl - the response is up to date number.
but for browser it takes like 10 more seconds to get that updated number.
MIs there a way to test a tail worker locally by having it bind to itself?
Sbut if I call do a cUrl call from terminal it returns updated value.
only for the same browser it takes longer.
only for the same browser it takes longer.
Jif I wanted a worker to refresh OAuth tokens, what is the best strategy? just set it up on an hourly cron schedule?
ZOn free workers, that's probably the best strategy. If you have the paid plan though, a better option is durable object alarms. That'll let you set the exact time you want to refresh that specific token at, and automatically retries if it fails.
ZIf you are on the free plan and storing the tokens in KV, watch out that there aren't two things writing to it at the same time. Since KV is eventually consistent, another worker running might not see the most up-to-date value and might update the value incorrectly.
Jso is your suggestion to save the Oauth token in a durable object? I haven't really used them before.
ACan I increase sub requests limit by calling them in another worker?
RHey, is
Object.groupBy avaliable inside the worker? it works locally but i want to be sure that it works when deployedRnice
