PHey.. I beat the status page :-)
Clol you did, hopefully didn't beat their internal monitoring though, status pages are just slow, approval and whatnot
Cmy silly api stuff started seeing errors at :40 or so
Cidk about server-side events but you're probably thinking of cpu time limits
Cyea you have unlimited duration as long as the user stays connected, but only 30s of cpu time on standard max per request. cpu time is only consumed when doing stuff with the cpu though, if you're just awaiting a fetch for example, 0 cpu time
Cit's 10ms for free and 30s max for standard, the 50ms is for bundled which is mostly gone, all non-ent workers paid got migrated to Standard
Cof course with standard you pay for cpu time though
CThat's not workers though just generic proxy
Cand pretty sure that just "works" because the timeout is only triggered if there's no body sent at all
Cidk what you'd accomplish with that but one runtime update and rip requests lol
CCyea, by keeping the connection open
CI don't think browsers could even do 100 requests lol, think they're limited to 4 connections per hostname or something
CWarning: When not used over HTTP/2, SSE suffers from a limitation to the maximum number of open connections, which can be especially painful when opening multiple tabs, as the limit is per browser and is set to a very low number (6). The issue has been marked as "Won't fix" in Chrome and Firefox. This limit is per browser + domain, which means that you can open 6 SSE connections across all of the tabs to www.example1.com and another 6 SSE connections to www.example2.com (per Stackoverflow). When using HTTP/2, the maximum number of simultaneous HTTP streams is negotiated between the server and the client (defaults to 100).ah yea hmm
https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events
