intial fastapi http transport

[aconchillo]

No description provided.

[aconchillo]

@kwindla The idea is that the developer subclasses FastAPIHTTPTransport and implements:

    async def input_generator(self, request: Request) -> AsyncGenerator[str | bytes, None]:
        pass

which will load the request body and will yield all the data in it. This way we don't force the format of the HTTP request.

and

    async def handle_request(self, request: Request) -> Response:
        pass

here the developer needs to call self.input().handle_request(request) and then return a response.

    async def handle_request(self, request: Request) -> Response:
        await self.input().handle_request(request)
        return EventSourceResponse(self.output().output_generator())

By not implementing a default handle_request() we allow the developer to return whatever they want. Doesn't need to be SSE.

[aconchillo]

@kwindla I think I'm going to close this for now. I believe there are probably better ways to work with HTTP. For example, I will now create a AsyncGeneratorProcessor that will have a serializer and will yield serialized frames. We can then use this generator in SSE for example or however we want.

For the input case we can just push frames to the pipeline. And the frames we push can be built from whatever we send from HTTP.

[aconchillo]

Closing. We can revisit if we really need an HTTP transport. The AsyncGeneratorProcessor I mentioned was added here #506