workerentrypoint and exportedfetchhandler
A workerentrypoint cannot be used as the main fetch handler correct?
the reason i ask because every example of an rpc workerentrypoint i've seen includes a dummy fetch usually with a response 404.
just wondering if instead of proxying directly to the rpc servicebinding fetch i could have it handle all incoming fetch?
the reason i ask because every example of an rpc workerentrypoint i've seen includes a dummy fetch usually with a response 404.
just wondering if instead of proxying directly to the rpc servicebinding fetch i could have it handle all incoming fetch?
