IBM Worklight 会话控制与后端服务器 [英] IBM Worklight session control with back-end server

查看:34
本文介绍了IBM Worklight 会话控制与后端服务器的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

有一个关于 IBM Worklight 服务器的问题,提前感谢您对此主题的任何评论.

Got a question on IBM worklight server, thanks in advance for any comments on this subject.

用户 --> WorkLight 服务器 --> 后端服务器

User --> WorkLight Server --> Back-end Server

(1) 使用 IBM Worklight Studio 设计了一个移动应用程序并部署到 worklight 服务器.

(1) Designed a mobile application with IBM worklight studio and deployed to worklight server.

(2) 必须使用 worklight 服务器作为第一个入口点(通过 worklight 服务器通过 LDAP 进行用户身份验证)

(2) Must use worklight server for the first entry point (user authentication by LDAP via worklight server)

(3) 此移动应用程序设计用于将巨大的文件大小(10mb 到 1gb)下载/上传到 worklight 服务器后面的后端服务器(请参阅工作流.)

(3) This mobile application designed for downloading/uploading huge file size (10mb to 1gb) to the backend server behind the worklight server (refer to the workflow pls.)

(1) 如何在 Worklight 服务器和后端服务器之间进行会话共享?

(1) How session sharing can be done in between worklight server and the back-end server?

(2) 如果无法进行会话共享,考虑到应用程序和后端服务器不知道通过跳过相同的已验证事务,移动应用程序下载/上传文件到后端服务器的最安全方法是什么?工作灯服务器?

(2) If session sharing cannot be done, what's the safest way that mobile application download/upload the files to the back-end server given that the application and back-end server do not know its the same authenticated transaction by skipping worklight server?

(3) 我是否对工作灯服务器架构有任何误解?据我所知,worklight 服务器只是一种网关和表示层,用于通过其框架部署移动应用程序.繁重复杂的计算逻辑应该由其他后端服务器处理.只要工作灯服务器网络 IO 足够宽以进行文件传输,在这种情况下工作灯服务器充当网关应该不成问题.对于文件传输,它不应该成为 CPU 的计算负担,因为它只是简单地从用户设备进出到后端服务器(worklight 作为中间人).

(3) Did I misunderstood anything from the worklight server architecture? as far as I know worklight server is just kind of gateway and presentation layer for deploying mobile application by its framework. Heavy and complex computation logic should be handled by other backend server. As long as the worklight server network IO is wide enough for file transfer, it shouldn't be a problem for the worklight server act as a gateway in this case. For file transfer, it shouldn't be a burden for CPU for computation as it is just simply in and out from the user device to the backend server (worklight as a middle man).

感谢您提出冗长的问题.

Thank you and sorry for the lengthy question.

推荐答案

(1) Worklight 服务器和后端服务器之间如何进行会话共享?

我可以假设您将使用工作灯适配器来进行文件传输吗?在这种情况下,将创建适配器和客户端之间的会话".更具体地说,如果我的适配器中存储了一个全局变量,并且我根据来自客户端的适配器调用修改了该变量,则该变量的状态将在后续请求中保持不变,并且该变量的状态将仅对调用客户端可见.(请注意,这在集群环境中并非总是如此,在集群环境中,客户端可能会调用单独的工作灯服务器上的适配器)

Can I make the assumption that you will be using a worklight adapter in order to do your file transfers? In that case, a "session" between the adapter and the client will be created. To be a bit more specific, if I have a global variable stored in my adapter and I modify the variable based on the adapter call from the client, the state of the variable will be maintained upon subsequent requests, and the state of that variable will only be visible to the calling client. (Just a note, this is not always true in clustered environments, where the client may be calling adapters on separate worklight servers)

(2) 如果无法进行会话共享,考虑到应用程序和后端服务器不知道其相同的身份验证,移动应用程序下载/上传文件到后端服务器的最安全方法是什么?通过跳过工作灯服务器进行交易?

如上所述,这可以通过适配器来实现.由于适配器可以通过身份验证进行保护,因此它知道客户端正在通过相同的身份验证事务调用.

As stated above, this can be achieved through adapters. Since adapters can be protected through authentication, it knows that the client is calling through the same authenticated transaction.

(3) 我是否对工作灯服务器架构有任何误解?据我所知,worklight 服务器只是一种网关和表示层,用于通过其框架部署移动应用程序.繁重复杂的计算逻辑应该由其他后端服务器处理.只要工作灯服务器网络 IO 足够宽以进行文件传输,在这种情况下工作灯服务器充当网关应该不成问题.对于文件传输,它不应该成为 CPU 的计算负担,因为它只是简单地从用户设备进出到后端服务器(worklight 作为中间人).

你一针见血.我个人没有在 worklight 服务器上进行过大量计算的任何性能测试,但如果它只是用作传递,那么你应该没问题.众所周知,Worklight 服务器能够处理相对大量的并发适配器调用,因此我相信您的设置会很好.

You hit the nail on the head. I haven't personally done any performance testing with a high amount of computations on the worklight server, but if it is being used simply as a passthrough then you should be fine. The worklight server has been known to be able to process a relatively high amount of concurrent adapter calls, so I believe you will be fine with your setup.

这篇关于IBM Worklight 会话控制与后端服务器的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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