Member Avatar for bhanu1607

Hi All,

This is Bhanu Teja M. I just wanted to write a online quiz application, which various people can participate in quiz from different locations. For this, i need to maintain a single screen for all users and maintain and display the same data,status across the all participents. Can any one suggest me, what type of java technlogies or frameworks or tools i can use for my application that to maintain the same status across the participent browsers and make visible the each participents action across the all participents.

Thanks & Regards
Bhanu Teja M.

  • 2 Contributors
  • 1 Reply
  • 321 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by deltascrow

Dani AI

Generated

For a quiz that keeps one “shared screen” and shows every participant’s actions in real time, avoid browser applets and build a web front end that receives push updates from a Java backend. Applets (JApplet / the Java browser plugin) are effectively obsolete — browser plugin/NPAPI support was removed by vendors — so a modern solution is HTML5 + WebSockets for low-latency, bidirectional updates. (en.wikipedia.org)

A practical Java stack that maps directly to your needs:

  • Spring Boot + Spring WebSocket (STOMP) for quick development of room/topic messaging and SockJS fallback for older clients.
  • Jakarta / Java WebSocket API (@ServerEndpoint) if you want a container-managed endpoint with a small footprint.
  • Vert.x or Atmosphere for highly concurrent, event-driven servers if you expect many simultaneous connections.
    Spring’s STOMP example shows how to broadcast to topics (one topic per quiz/room) so every client sees the same screen. (spring.io)

State, scaling and persistence:

  • Keep the quiz state authoritative on the server (timers, accepted answers, scoring). Don’t rely on client clocks.
  • Persist results with JDBC/JPA to a relational DB (or a fast NoSQL store for high write rates).
  • For multi-server deployments use a central pub/sub or broker (Redis pub/sub or a message broker like RabbitMQ) to forward real-time events between app instances. This lets you horizontally scale without losing sync. (redis.io)

Minimal server-side WebSocket sketch (Jakarta):

@ServerEndpoint("/quiz/{room}")
public class QuizEndpoint {
  @OnOpen public void open(Session s,@PathParam("room")String r){ /* register */ }
  @OnMessage public void msg(Session s,String p,@PathParam("room")String r){ /* validate, broadcast */ }
  @OnClose public void close(Session s,@PathParam("room")String r){ /* cleanup */ }
}

Security / gotchas: use WSS/TLS, validate Origin and auth on handshake, enforce message size and rate limits, and make the server authoritative for timers/answers. See OWASP WebSocket guidance for hardening checks.

Notes: this builds on ’s requirement for a single shared view and responds to ’s applet suggestion — but applets are no longer viable in modern browsers.

Member Avatar for deltascrow

Create an applet, link it to a database. Then, when anyone accesses your Applet, retrieve the relevant data and show it to the user(s). Create a log-in interface so that each quiz participant can access the system, etc. Have a look t JApplet and JDBC. Does this help?

http://www.oracle.com/technetwork/java/overview-141217.html
http://docs.oracle.com/javase/6/docs/api/javax/swing/JApplet.html

Edited by deltascrow
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.