Hello all,
I am deciding between which option to go with between WebSockets and server handler for an enterprise web application.
use case :
User base ?- 300k users.
Concurrent connections expected? - 10% during the day - 30k.
Two-way communication required? Only on the chat page.
What i like about WebSockets is that the entire coding can be done on B4J(using jqueryelement) and not have to code using client side javascript.
Having said that, since WebSockets maintain a connection between the client and the server, is it advisable to use WebSockets?
Do they have any drawbacks, in case if they are used for eg pages like login page, show user info etc.
Using handlers i am able to achieve the same results by making AJAX calls. just that i have to code javascript and all the code is available on the client-side.
Which option would you recommend and if you can please help me understand why?
Can Jetty server handle this volume?
Thank you so much.
I am deciding between which option to go with between WebSockets and server handler for an enterprise web application.
use case :
User base ?- 300k users.
Concurrent connections expected? - 10% during the day - 30k.
Two-way communication required? Only on the chat page.
What i like about WebSockets is that the entire coding can be done on B4J(using jqueryelement) and not have to code using client side javascript.
Having said that, since WebSockets maintain a connection between the client and the server, is it advisable to use WebSockets?
Do they have any drawbacks, in case if they are used for eg pages like login page, show user info etc.
Using handlers i am able to achieve the same results by making AJAX calls. just that i have to code javascript and all the code is available on the client-side.
Which option would you recommend and if you can please help me understand why?
Can Jetty server handle this volume?
Thank you so much.