Cloudflare Workers derive their name from Web Workers, and more specifically Service Workers, the W3C standard API for scripts that run in the background in a web browser and intercept HTTP requests. Cloudflare Workers are written against the same standard API, but run on Cloudflare's servers, not in a browser.
The possible uses for Workers are infinite. Here are some ideas seen in the beta:
Well, this is another way of creating vB modifications created outside vBulletin! The plugin code resides in Cloudflare and not in vBulletin but it can modify anything what vBulletin loads on the browser. See this sample in action. This sample changes the background of vbmods.rocks to black and changes all instances of "glennrocksvb" into "Glenn rocks vBulletin!".
https://cloudflareworkers.com/#135c7...//vbmods.rocks
The possible uses for Workers are infinite. Here are some ideas seen in the beta:
- Route different types of requests to different origin servers.
- Expand HTML templates on the edge, to reduce bandwidth costs at your origin.
- Apply access control to cached content.
- Redirect a fraction of users to a staging server.
- Perform A/B testing between two entirely different back-ends.
- Build "serverless" applications that rely entirely on web APIs.
- Create custom security filters to block unwanted traffic unique to your app.
- Rewrite requests to improve cache hit rate.
- Implement custom load balancing and failover logic.
- Apply quick fixes to your application without having to update your production servers.
- Collect analytics without running code in the user's browser.
- Much more.
Well, this is another way of creating vB modifications created outside vBulletin! The plugin code resides in Cloudflare and not in vBulletin but it can modify anything what vBulletin loads on the browser. See this sample in action. This sample changes the background of vbmods.rocks to black and changes all instances of "glennrocksvb" into "Glenn rocks vBulletin!".
https://cloudflareworkers.com/#135c7...//vbmods.rocks
Comment