Is the ComponentRequestHandler using the same websocket as session?

Hi everyone,

Currently the custom component request handler in the Streamlit library doesn’t seem to be going through websocket of the session. Can someone confirm this? And if so, is there a reason for it? It is a bit out of my league :sweat_smile:

I am asking because we are still experiencing custom component rendering issues in serverless / autoscaled deployments (e.g., Google Cloud Run); suspecting it is because custom component requests sometimes end up in different container instances, and if the receiving instance does not have the component registered yet, the requests fail and thus the rendering fails.

Assuming this is the case, if the custom component requests went through the websocket, Google Cloud Run would actually ensure “stickiness” (all requests from the websocket end up in the same container instance).

Thanks in advance!

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.