LL
RL
WWL
HL
A
O
DALOOO
A
ᎡW‘User Workers’ meaning… These would be workers that I am deploying on behalf of the customer… do customers have visibility of these workers/source code from their dashboard? I presume not (I would hope)
D1 and R2 access from these User Workers… this would be to MY instance yes? And I would be responsible for ensuring segregation of data as appropriate?
Placing limits for customers… This would be something I would need to implement myself from the dispatch worker correct?
Ꭱ
W
What exactly is the 
tag (not tags) field on the script object?
J
JJJJ
J
J
J
B
Y
Workers for Platforms Scripts (I have this section in our bill).
D
) custom hostnames so that customers can point their domain to my worker. But I can't get this to work. The fallback origin is a worker, I've setup the AAAA 100::, origin seems fine, hostname added, validation completed – but when I access the customer domain (that should be now pointing to my fallback origin (worker)), I always get a cf page with 522. 
Dwrangler@dispatch-namespaces-dev release seems to be 4 months old
R
BD
A
D
IIDIDI
tagtagsscript export default {
async fetch(req, env) {
const worker = env.DISPATCHER.get("customer-worker-1");
return await worker.fetch(req);
},
};Workers for Platforms ScriptsAAAA 100::wrangler@dispatch-namespaces-devexport default {
async fetch(request, env) {
try {
let workerName1 = "worker1";
let userWorker1 = env.dispatcher.get(workerName1);
let result1 = await userWorker1.fetch(request);
let workerName2 = "worker2";
let userWorker2 = env.dispatcher.get(workerName2);
let result2 = await userWorker2.fetch(request);
} catch (e) {
if (e.message.startsWith('Worker not found')) {
return new Response('', { status: 404 });
}
return new Response(e.message, { status: 500 });
}
},
};