在网络或网站应用方面,请求 - 响应和推挽服务模型之间的关键差异是什么? [英] Whats The Key Diffrence Between Request-Response and Push-Pull Service Model In Terms Of Network Or Website Application?

查看:59
本文介绍了在网络或网站应用方面,请求 - 响应和推挽服务模型之间的关键差异是什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

最近我做了开始学习Node.js abd从那时起我确实想到了nower day`s node.js被广泛使用,因为它支持 Push-Pull / Publish-subscript 以及 请求 - 响应这两种编程能力。

但是在阅读了6到8篇文章后我仍然感到困惑关于它们之间的差异。



任何帮助都会受到影响。



在此先感谢。

解决方案

我确实尝试解决这个问题



在请求 - 响应中,客户端不会注意到这一点消息,直到他将请求发送到服务器,使用ajax或只是移动到另一个页面(执行Http请求)。



这里的主要问题是更新是不是实时/生活。在他再提出请求之前,客户不知道他是否有任何更新。



另一方面,在推拉关系中,服务器推动更新客户端,以便客户通知他收到的实时消息,而无需等待接收更新的下一个请求。



请纠正我如果我错了

Recently I did Start To Learn Node.js abd As of That i did Figure out that nower day`s node.js is widely use cause it supports Push-Pull/Publish-subscript as well as Request-Response both kind of Programming Capability.
But After Reading 6 to 8 article still i have confusion on the diffrance between them.

Any Help Would Be Appriciated.

Thanks In Advance.

解决方案

I did Try To SOLVE THIS

In request-response, the client won't notice about that message until he will send a request to the server, using ajax or simply moving to another page (Executing Http request).

The main problem here is that the updates are not real-time/live. The client doesn't know if there are any updates for him until he make a further request.

On the other hand, in push-pull relation the sever pushes the updates to the client, so the client informed about the message he receives live, without waiting for the next request to receive the update.

Please Correct Me If I am Wrong


这篇关于在网络或网站应用方面,请求 - 响应和推挽服务模型之间的关键差异是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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