WebSockets & Real-Time Systems with Spring · درس

إدارة جلسات المستخدمين

نفّذوا إدارة متقدمة لجلسات مستخدمي WebSocket، مع ربط جلسات HTTP بجلسات WebSocket.

إدارة جلسات المستخدمين درس مجاني في WebSockets & Real-Time Systems with Spring على CoddyKit. هذا هو الدرس 3 من أصل 4. يمكنك قراءة الدرس كاملاً أدناه مجاناً — ثم تمرن عليه مباشرة في المتصفح باستخدام محرر أكواد مدمج ومدرس ذكاء اصطناعي متاح 24/7. هذا الدرس جزء من مسار التعلم في WebSockets & Real-Time Systems with Spring، وتقدمك يتزامن عبر الويب وتطبيق CoddyKit. تتضمن دورة WebSockets & Real-Time Systems with Spring 4 دروس في المجموع.

بعض أجزاء هذا الدرس لم تُترجم بعد وتظهر باللغة الإنجليزية.

Understanding User Sessions

In web applications, a "session" helps a server remember a user across multiple requests. It's like a temporary memory for each user.

For traditional HTTP, sessions are often managed with cookies. They allow you to store user-specific data, like login status or cart items, between page loads.

WebSockets: Session Challenges

Unlike HTTP, WebSockets establish a persistent, full-duplex connection. This connection doesn't inherently carry the same session context as an HTTP request.

This means if a user logs in via HTTP and then opens a WebSocket, the WebSocket connection won't automatically know who the user is without specific setup.

HTTP Session: Short-lived, request-response.
WebSocket Session: Long-lived, persistent connection.

Bridging HTTP & WebSocket Sessions

To build rich real-time applications, you often need the WebSocket connection to know about the user's HTTP session context.

For example, you might need to know if a user is authenticated, their user ID, or other profile details that were established during their initial HTTP login.

Spring provides mechanisms to "bridge" this gap during the WebSocket handshake.

The Handshake Interceptor

Spring's primary tool for linking HTTP and WebSocket sessions is the HttpSessionHandshakeInterceptor.

This interceptor runs during the WebSocket handshake, which is the initial HTTP request that upgrades to a WebSocket connection. It can copy attributes from the current HTTP session to the WebSocket session.

What it does: Copies HTTP session attributes.
When it runs: During the WebSocket handshake.

Configuring Session Interceptor

To use the HttpSessionHandshakeInterceptor, you need to register it within your WebSocket configuration. This tells Spring to apply the interceptor when a WebSocket connection is being established.

It's typically added in your WebSocketMessageBrokerConfigurer implementation:

public class WebSocketConfig extends AbstractWebSocketMessageBrokerConfigurer {
  @Override
  public void registerStompEndpoints(StompEndpointRegistry registry) {
    registry.addEndpoint("/ws")
            .addInterceptors(new HttpSessionHandshakeInterceptor())
            .withSockJS();
  }
}

Accessing Linked Session Data

Once the HttpSessionHandshakeInterceptor has done its job, you can access the copied HTTP session attributes within your WebSocket message handlers.

Commonly, you'll want to access the Principal (representing the authenticated user) or other custom attributes you've stored in the HTTP session.

@Controller
public class MyWebSocketController {
  @MessageMapping("/hello")
  public void handleMessage(@Payload String message, Principal principal) {
    String username = principal.getName();
    System.out.println("Message from " + username + ": " + message);
    // ... use username for user-specific logic
  }
}

WebSocket-Specific Data

Besides copying HTTP session data, you can also store information directly within the WebSocketSession itself. This data is specific to that particular WebSocket connection.

This is useful for managing connection-specific states, like a user's current chat room, notification preferences for this connection, or other transient data.

@EventListener
public void handleSessionConnect(SessionConnectedEvent event) {
  StompHeaderAccessor accessor = StompHeaderAccessor.wrap(event.getMessage());
  WebSocketSession session = (WebSocketSession) accessor.getSessionAttributes().get("webSocketSession");
  if (session != null) {
    session.getAttributes().put("customKey", "customValue");
  }
  System.out.println("User connected: " + accessor.getUser().getName());
}

Managing Session Lifecycle

Spring allows you to listen to WebSocket session lifecycle events. This is crucial for cleaning up resources or updating user status when connections are established or closed.

You can use @EventListener with SessionConnectedEvent and SessionDisconnectEvent to react to these changes.

SessionConnectedEvent: Fired when a new STOMP session is established.
SessionDisconnectEvent: Fired when a STOMP session is closed.

Runnable: Handshake Interceptor

This Spring Boot example configures a WebSocket endpoint with HttpSessionHandshakeInterceptor. When a client connects, the interceptor helps link the HTTP session (if any) to the WebSocket session.

We demonstrate a simple message handler that could access the authenticated user's Principal. If Spring Security were enabled, principal.getName() would return the logged-in username.

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Configuration;
import org.springframework.messaging.handler.annotation.MessageMapping;
import org.springframework.messaging.simp.config.MessageBrokerRegistry;
import org.springframework.stereotype.Controller;
import org.springframework.web.socket.config.annotation.EnableWebSocketMessageBroker;
import org.springframework.web.socket.config.annotation.StompEndpointRegistry;
import org.springframework.web.socket.config.annotation.WebSocketMessageBrokerConfigurer;
import org.springframework.web.socket.server.support.HttpSessionHandshakeInterceptor;
import java.security.Principal;

@SpringBootApplication
@EnableWebSocketMessageBroker
public class WebSocketSessionApp {
  public static void main(String[] args) {
    SpringApplication.run(WebSocketSessionApp.class, args);
  }

  @Configuration
  public static class WebSocketConfig implements WebSocketMessageBrokerConfigurer {
    @Override
    public void configureMessageBroker(MessageBrokerRegistry config) {
      config.enableSimpleBroker("/topic");
      config.setApplicationDestinationPrefixes("/app");
    }

    @Override
    public void registerStompEndpoints(StompEndpointRegistry registry) {
      registry.addEndpoint("/ws")
              .addInterceptors(new HttpSessionHandshakeInterceptor())
              .withSockJS();
    }
  }

  @Controller
  public static class WebSocketGreetingController {
    @MessageMapping("/hello")
    public void greeting(Principal principal) {
      if (principal != null) {
        System.out.println("Message from authenticated user: " + principal.getName());
      } else {
        System.out.println("Message from unauthenticated user (Principal is null).");
      }
    }
  }
}

Quick Check: Handshake Interceptor

Test your understanding of the HttpSessionHandshakeInterceptor.

Recap: Session Management

We've explored how to manage user sessions in Spring WebSocket applications, particularly how to link HTTP session context to WebSocket sessions.

The HttpSessionHandshakeInterceptor is key for copying HTTP session attributes during the handshake.
You can access authenticated user information (Principal) in WebSocket handlers.
@EventListener helps manage connection and disconnection events.

Proper session management ensures your real-time features are personalized and secure for each user.

الأسئلة الشائعة

هل درس «إدارة جلسات المستخدمين» مجاني؟

نعم — نص درس «إدارة جلسات المستخدمين» كامل متاح مجاناً هنا على الويب. لتمرينه بشكل تفاعلي (محرر أكواد مدمج ومدرس ذكاء اصطناعي متاح 24/7) وفتح باقي دورة WebSockets & Real-Time Systems with Spring، انتقل إلى CoddyKit PRO. تتضمن دورة WebSockets & Real-Time Systems with Spring 4 دروس في المجموع.

ماذا ستتعلم في «إدارة جلسات المستخدمين»؟

نفّذوا إدارة متقدمة لجلسات مستخدمي WebSocket، مع ربط جلسات HTTP بجلسات WebSocket. تتمرن على WebSockets & Real-Time Systems with Spring مع أكواد عملية تشغلها مباشرة في المتصفح، ومدرس ذكاء اصطناعي متاح 24/7 يجيب على أسئلتك أثناء عملك.

هل أحتاج إلى خبرة سابقة لأبدأ WebSockets & Real-Time Systems with Spring؟

لا تُشترط خبرة سابقة. WebSockets & Real-Time Systems with Spring على CoddyKit منظم للمبتدئين حتى المتقدمين، لذا يمكنك البدء من هنا أو من البداية والتقدم بسرعتك الخاصة. هذا هو الدرس 3 من أصل 4.

كم من الوقت يستغرق درس «إدارة جلسات المستخدمين»؟

معظم دروس CoddyKit تستغرق حوالي 5–10 دقائق. كل منها موجز وتفاعلي، لذا تحرز تقدماً مستمراً وتستأنف من حيث توقفت عبر الويب والتطبيق.

هل يمكنني كتابة وتشغيل أكواد في درس WebSockets & Real-Time Systems with Spring هذا؟

نعم. كل درس في WebSockets & Real-Time Systems with Spring يتضمن محرر أكواد مدمج، لذا تكتب وتشغل أكواداً حقيقية مباشرة في متصفحك وتحصل على تعليقات فورية من الذكاء الاصطناعي — بدون إعداد محلي.

جميع الدروس في هذه الدورة

← العودة إلى WebSockets & Real-Time Systems with Spring