9 replies

Thanks @FlikTeoh, totally agree the docs

Thanks @FlikTeoh, totally agree the docs are impressive, I have read the RPC documentation and implemented it across other workers, this scenario is slightly different from documented. Or at least I couldn't work out from the docs how to implement my scenario...

I have a worker with the following simplified code:

import { Hono } from 'hono'
const app = new Hono()

app.get('/', (c) => c.text('Hello Cloudflare Workers!'))
app.get('/analyse', (c) => c.text('Hello Analyse endpoint!'))

export default app

import { Hono } from 'hono'
const app = new Hono()

app.get('/', (c) => c.text('Hello Cloudflare Workers!'))
app.get('/analyse', (c) => c.text('Hello Analyse endpoint!'))

export default app

In order to do a service to service binding I have the RPC or fetch option. With the RPC approach I have to export a class that extends

WorkerEntrypoint

WorkerEntrypoint

, in which case how do I also export the endpoints?

If I want to use the HTTP fetch interface how would I export a fetch handler and also the other endpoints via Hono?

I'm starting to wonder if there is a problem with my solution design, might rethink it, in the meantime any examples or pointers appreciated.

Cloudflare Developers•2y ago•

9 replies

jason

Thanks @FlikTeoh, totally agree the docs

import { Hono } from 'hono'
const app = new Hono()

app.get('/', (c) => c.text('Hello Cloudflare Workers!'))
app.get('/analyse', (c) => c.text('Hello Analyse endpoint!'))

export default app

import { Hono } from 'hono'
const app = new Hono()

app.get('/', (c) => c.text('Hello Cloudflare Workers!'))
app.get('/analyse', (c) => c.text('Hello Analyse endpoint!'))

export default app

In order to do a service to service binding I have the RPC or fetch option. With the RPC approach I have to export a class that extends

WorkerEntrypoint

WorkerEntrypoint

Thanks @FlikTeoh, totally agree the docs

Similar Threads

Thanks @FlikTeoh, totally agree the docs

Similar Threads

Similar Threads

Similar Threads