They got free plans if I only test it a few times?
They got free plans if I only test it a few times?
CI'm not even sure about all this new stuff you feel, I'm old-school write it up from scratch and just host more servers and IPC them right.
Ddoing that is a lot of work imo. Once you get the hang of Workers, it's much easier.
CThat may be a solid solution though cause I worry about a single broker keeping say many media servers state of how many weights left, or user slots and if this can make it so I can run many core brokers
Ckeeping it stateful and savage ouuf.
DWorkers can be used on the free plan, just not Workers Durable Objects
CDave I'm the type of guy who can't trust other code, if I write it and bullet-proof it, I know I'm safe and can laugh.
CBut dang, what plan is that for then?
CI was considering PRO for the firewall improvements
DCloudflare scales Workers almost infinitely for many customers.
CYeah I saw I just don't get how it can for a stateful system, that's amazing.
CSo you work ai.moda?
Dthe nice thing is many things don't have to be that stateful when you think about it. 
CFor me, it's mostly who is in a room, who is on what media server, the usage of those media servers and calculating where one should go
Cso a single broker for me has a limit of say 100 media servers, 20K users and a broker is a single core.
CI must keep certain track to ensure messages from one user makes it to an entire room or a specific user's inbox while in session.
CBroker must assign chat servers to users/rooms. it's a lot of state checks.
Dimo the Pro plan ($240/year) + Workers paid plan ($5/m) is the best bang for buck.
DDurable Objects using WebSockets is definitely what you want.
CI'm considering it, I just have a grand time with the given firewall and my ability to scout bad ASNs free has worked best.
CYou get that in PRO?
CI've not seen the option as free user otherwise I may apply for a plan haha
CYou know what TY for that, I may explore that soon, but yo if you test that let me know how it works when you got concurrency slamming it.
CI'm intriqued.
DShould work fine.
CGG
CCool site, should set the footer to automatically adjust copyright year 
C@dave | ai.moda haha
Dthanks; it's pretty out of date, we need to fix a bunch of things, but hasn't been a high priority atm
CI feel that, I've re-written my entire site twice now, first stage was rough, second is alright and cutting it but third I think should improve much of the UI/etc.
CGets a bit overwhelming the little things, I feel that 10000%. I only fix emergencies currently on my current production copy, and on my development add all these things to the fixes carefully.
But again TY for that tidbit of information, I really want to try that service out and benchmark it.
But again TY for that tidbit of information, I really want to try that service out and benchmark it.
Uthats not how copyright works
CFunny cause it's generally acceptable.
Ugenerally acceptable by people who arent in law*
CSuch varies by countries, intellectual property is gauranteed for the most part.
C
CCIPO doesn't need to clarify my content, it's promised world wide since the day I hit the archives.
SI linked my KV namespace with my worker, but when I try to use my variable name in my worker, it says it cannot find it
UCan you give the actual error message and relevant code?
SI have a KV namespace named KV, and the final line with KV.get("data") has the KV underlined red saying cannot find any KV:
addEventListener('fetch', event => {
event.respondWith(handleRequest(event.request));
});
async function handleRequest(request) {
if (request.method === 'POST' && request.url.endsWith('/submit-form')) {
const formData = await request.json();
await saveFormData(formData);
return new Response(null, {
status: 302,
headers: {
'Location': '/thankyou.html',
},
});
}
return new Response('Invalid request', { status: 400 });
}
async function saveFormData(formData) {
const data = await KV.get("data");
addEventListener('fetch', event => {
event.respondWith(handleRequest(event.request));
});
async function handleRequest(request) {
if (request.method === 'POST' && request.url.endsWith('/submit-form')) {
const formData = await request.json();
await saveFormData(formData);
return new Response(null, {
status: 302,
headers: {
'Location': '/thankyou.html',
},
});
}
return new Response('Invalid request', { status: 400 });
}
async function saveFormData(formData) {
const data = await KV.get("data");
CDoes const data = await KV.get("data", "json"); (dismiss this)
help?
help?
Sno it doesn't
CHow are you defining KV?
S
CDouble check your configurations
Cyour code could be wrong/etc.
UOh a red underline just means you dont have types setup for it in ur code editor. Also you should upgrade to the more modern module worker format instead of service worker
Ssorry this is my first time using workers, how do I do both of those things?
UAssuming your worker literally only does the one thing you sent I would just make a new worker from scratch. How did you make the worker you currently have?
Si simply clicked create worker, and then linked it as a route to my site, and linked my kv namespace to it
