-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about facil.listen() argument #36
Comments
Hi @SteMMo33 , I'm sorry for the late response, I'm on vacation and don't have access to my computer on a regular basis. I think I see the problem, but I'm not not sure... I don't know what example you are pointing to, but it could be that the example uses the 0.5.x version API instead of the 0.6.x version API. In the new API please use the Please note that the If you have any more questions, please let me know. I'll answer as soon as I can. Kindly, |
Hi Bo,
In my understanding the library shoud handle the initial autentication for the websocket, is it? thanks again, PS: RedSox #1 :)) |
@SteMMo33 Hello, Yes, the example code you chose is from the core module (included through The WebSocket protocol is part of the HTTP and WebSockets module, which you can use by including the A WebSockets example should available on the Website. Like many of the examples, the API in the example is dependent on the release version. I believe the API on the website reflects the latest 0.6.x release, but it might be updated soon to use the master branch (the upcoming 0.7.0 release API) which includes some changes to the pub/sub logic and API. As for the The The callback behaves the same with WebSocket connections, which use You don't have to use it. Bo. |
Hi there,
I'm writing a simple websocket server based on a sample from the site.
I needed to change some rows of code to compile, 'cause they have a different prototipes.
In particular
facil_listen(
.port = "7681",
.on_open = create_protocol,
Now create_protocol() is
static inline void create_protocol(intptr_t uuid, void * arg) {
returns nothing and then I'm wondering how to return the pointer to protocol_s structure.
In this way the connection is not possible.
Thanks!
The text was updated successfully, but these errors were encountered: