REST API调用的粘性会话 [英] Sticky Session for Rest API Calls

查看:92
本文介绍了REST API调用的粘性会话的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

对于具有粘性会话的基于浏览器的请求,真正的负载平衡器可以将请求限制为集群中多个JVM中的同一JVM.

For browser based request with sticky session true load balancer can restrict request to same JVM out of multiple JVMs in a cluster.

但是,如果请求来自REST客户端而不是任何浏览器,那么即使将粘性会话设置为true,负载均衡器如何将请求限制到同一JVM?任何想法,请.

But in case request is coming from REST client rather any browser, how the load balancer can restrict requests to same JVM even sticky session is set as true? Any Idea please.

推荐答案

使REST客户端调用REST API,并且REST API应该是无状态的,即有关请求处理的完整信息应该出现在请求本身中,因此请求不应依赖在任何会话数据上.

REST client is made to call REST API and REST APIs should be stateless i.e. complete information about processing of request should be present in request itself, thus request should not dependent on any session data.

如果您的API依赖于会话数据,那么实际上它并不遵循REST的某些原理.

If your API is dependent on session data then in actual it is not following some principles of REST.

这篇关于REST API调用的粘性会话的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆