Dear Christian,
we are currently thinking of a solution based on adding attributes to
the websocket with the dedicated function. Then filtering out the right
websocket to send a message to based on the attribute value.
as a prerequisite it has to be possible to pass query-parameters to the
ws:connect endpoint url?
From the JS point of view "ws://myserver.com/path?param=1" is a valid
ws url. Is the server side code able to handle this?
Thanks a lot,
Marco.
On 23/06/23 16:46, Christian Grün wrote:
Hi Marco,
As most web applications open only one or a few websockets at the same
time, we decided against supporting wildcards.
Feel free to share background information on your use case with us,
maybe you can convince us to get active ;·)
Ciao,
Christian
On Fri, Jun 23, 2023 at 11:21 AM Marco Lettere <m.lett...@gmail.com> wrote:
Dear all,
so I just found out that it is not possible to create websockets bound
to dynamic paths.
If I try a websocket connection to
declare
%ws:connect('/notification/subject/{$subject}')
function log:subject() {};
I get an error (without significant logs). Whereas
declare
%ws:connect('/notification/subject/one')
function log:subject() {};
works well.
Does this have a motivation? Is there another way of meeting the
requirement of having dynamic websocket channels?
Thanks in advance,
Marco.
