The advantages you have outlined in file <apps/showcase/src/main/webapp/async/index.html> (quoted below) is precisely the reason for my post . Now I feel struts2 is a complete framework for any imaginable application. Struts 2 is now a simple yet powerful , adaptable framework. Please do what you need to do for version 2.6 to refine the last piece.
<br/> <h2>Example: A minimal chat room using server push</h2> <h3>Open current page in different tabs, browsers and computers then send messages.</h3> <h4>This is a minimal chat room which uses server push to retrieve new messages. It doesn't poll the server frequently to check if a new message is available to display. Instead it waits for the server to push back new messages. This approach has two obvious advantages: low-lag communication without requests being sent, and no waste of server resources and network bandwidth.</h4> <h5>Reference: <a href=" https://www.javaworld.com/article/2077995/java-concurrency/java-concurrency-asynchronous-processing-support-in-servlet-3-0.html "> Asynchronous processing support in Servlet 3.0</a></h5> On Sun, 24 Nov 2019, 08:09 Yasser Zamani, <yasserzam...@apache.org> wrote: > Hi Zahid, > > Additionally, AFAIK... > > If your users are a lot, then I think you have to wait for Struts 2.6 > release where I've added support for Async actions. For an instance usage > see my example at [1] (you can try it via running Struts 2.6 snapshot > showcase - it's a simple chat room i.e. classic usage of server push). > > Otherwise or anyway, for now, you can try if Struts ExecAndWait is able to > handle your users. > > Regards. > > [1] > https://github.com/apache/struts/pull/179/commits/aee171c3b8ad401006612c4df44ed540fb2ed7e3 > > >-----Original Message----- > >From: M Huzaifah <mhuzaifah.i...@gmail.com> > >Sent: Friday, November 22, 2019 6:57 AM > >To: Struts Users Mailing List <user@struts.apache.org> > >Subject: Re: Update views how to ? > > > >Hi, > > > >You should use stream mecanism for that case. What i've done, i used JMS, > >message-broker, which mean the browser always listen to message-broker > server > >using websocket (STOMP,AMQP,etc). When backend push message to the broker > >server, browser automatically receive and render the message to the > browser. I > >use ActiveMQ over MQTT, and render the message using javascript in > browser. > > > >You can find another stream mecanism or reactive application example out > there. > > > >Regards > > > >On Fri, Nov 22, 2019, 10:06 Zahid Rahman <zahidr1...@gmail.com> wrote: > > > >> Hi, > >> > >> I have an admin screen (jsp) where the administrator updates values > i.e. > >> current weather temperature, cricket , football score, death counter > >> showing people killed by knife crime in a city, natural causes , car > >> accidents etc. > >> > >> > >> I have at least two users who are looking at the current temperature > >> or game score etc. (JSP). > >> > >> Once the administrator updates the values , the data viewed by the two > >> users In their browser is now stale data , due to the fact the web > >> browser is based on a stateless pull model. > >> > >> Is there an example app or maven archetype which shows how I can > >> update or refresh the views (JSPs viewed in browser) in all the user > >> sessions [views ] from inside the running application server using the > >> struts2 framework. > >> >
