You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @ddeaguiar! Do you know of anyone who has tried to get pedestal.ions (or Ions, generally) working with WebSockets? I have been trying to determine whether using WebSockets with Ions is feasible or not, given AWS constraints and the inability to override server configuration in Datomic Cloud.
I see in the README that one cannot simply "turn on" async functionality with pedestal.ions, but I'm not sure whether that precludes the use of WebSockets or not, and whether or not the limitations could be worked around.
Apologies if I've missed something obvious in my search.
The text was updated successfully, but these errors were encountered:
Hi @Usernms! I have not tried using WebSockets with pedestal.ions or Datomic Ions in general but I've gotten some field reports that WebSocket integration via API Gateway is pretty easy to setup. I don't think you will require async processing when integrating with API GW in this way.
@ddeaguiar thanks for the quick response! And apologies for the delay. That tracks with what I've been able to scrap together about making this work. I'll report back here with any results once I get some time to poke this again.
Hi @ddeaguiar! Do you know of anyone who has tried to get
pedestal.ions
(or Ions, generally) working with WebSockets? I have been trying to determine whether using WebSockets with Ions is feasible or not, given AWS constraints and the inability to override server configuration in Datomic Cloud.I see in the
README
that one cannot simply "turn on" async functionality withpedestal.ions
, but I'm not sure whether that precludes the use of WebSockets or not, and whether or not the limitations could be worked around.Apologies if I've missed something obvious in my search.
The text was updated successfully, but these errors were encountered: