Currently, in the front-end server, the NeoActor is sending the message directly to the berryClient. It works because the front-end and the middleware live in the same server which will not be the case if we want to make Cloudberry a general purpose middleware.
Now, since we have the /berry API, the NeoActor should send an HTTP request to http://hostname:port/berry instead of an actor message and then receive a stream of HTTP chunked results.
You can read this documentation about how to use it to handle a stream of responses.
Currently, in the front-end server, the
NeoActor
is sending the message directly to theberryClient
. It works because the front-end and the middleware live in the same server which will not be the case if we want to make Cloudberry a general purpose middleware.Now, since we have the
/berry
API, theNeoActor
should send an HTTP request tohttp://hostname:port/berry
instead of an actor message and then receive a stream of HTTP chunked results.You can read this documentation about how to use it to handle a stream of responses.