Search Results

WebSocket is a type in jServer. Name your WebSocket class differently.

WebSockets is an extension to the http protocol that was designed exactly for such use cases where you want to break the request - response pattern. There is really no reason to "fight" http and make it act like a limited WebSocket.
link: @Erel I understand a Websocket solution may be trivial, but I wanted to create a server which responds with JSON, as does the server I described in th
link: I think I haven’t seen any sample in this forum that make use of websocket and http at the same time.

I am really confused with your answer.. See: https://www.b4x.-hello-world-web-app.39808/ Which states: “The WebSocket itself (ws in this case) allows you to call any JavaScript function and also to create JavaScript code at runtime and run it (eval / new function).”

I think WebSocket is a special class from jserver, and its event name is fixed as WebSocket. we can't add the element Event to jserver.xml like other classes for hints, otherwise on IDE it looks that there will be a prefix EventName, if you want some tips, add the element Comment for this. 154756

Now the firsts suggestions are more clear to me. Maybe a websocket is more efficient to exchange info between the two apps and involve only local network traffic. Thanks again.

'QS' (Questionnaire Sequencer), is my eLearning and questionnaire system that presents material to the client in a logic driven way. It is structured as an ordered sequence of text and media (questionnaires, quizzes, audio slide shows and video clips). The system has had many variants in the past u
link: I have updated the app to include a database, a login procedure, administrative functions and more examples. In the examples with a user login, users
link: t would be interesting to have this running in ABMaterial.

Why not. jWebSocketClient appears to be wrap of org.eclipse.jetty.websocket.client.WebSocketClient - a standard websocket implementation. I see nothing jServer specific in the library.
link: Very true. It is not exactly a limitation, it is more of a different use case. jServer WebSocket was built to interact with browsers (and in a specif

A server shut down/restart will clear all active and orphaned sessions. Any sessions after starting the server back up will be new sessions. A new instances of a WebSocket will always be created if a WebSocket is closed or otherwise disconnected. A new WebSocket is not just triggered programmaticall
link: Reading (and badly answering) this thread: https://www.b4x.-about-jserver-websocket-handle.95966/ I learned that if a websocket was closed, the relate
link: :confused: Probably I don't need an answer (at least to solve "my problem", although it is still a good question, I think), because I can simply use
link: You are confusing different things. Each time that a client connects, a new WebSocket handler instance is created. This is not related to the http ses

Yeah, that is what I was thinking of doing, but wasn't sure if there was a way in getting it directly.
link: Create a DIV/P Tag in your website (giving it a unique ID), output the var in this DIV/P and fetch the content similar to the code in the other thread
link: Hi, This is a follow up to my other thread (https://www.b4x.-get-html-selected-option-id.125643/) If on my webpage I have a variable, is there a way

websocket is on top of HTTP, which is on top of TCP Network failure makes a big latency (up to 20 sec or more ) before it triggers disconnec or error event During this time, you keep sending and losing messages Regards
link: HTTP/HTTPS. Socket.io uses WebSockets (when available) for communications. Please note Socket.io preferred communication channel is WebSockets, but if

Powered by ColBERT