关于appengine的聊天应用程序 [英] chat application on appengine

查看:282
本文介绍了关于appengine的聊天应用程序的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我愿意在App Engine上实施聊天网站。但我发现App Engine不允许我使用服务器推送。 (因为它将在30秒后杀死响应)。

I am willing to implement a chat website on App Engine. But I found that App Engine will not allow me to go with server push. (as it will kill the response after 30 sec).


  1. 那么可以使用另一种可以使用
    的方法吗?轮询会导致糟糕的用户
    体验吗?用户
    的含义是否需要等待一段时间才能从服务器中检索新消息?

  1. So whats the other method that can be used? Will polling cause bad user experience? Meaning will the user have to wait for some time to retrieve new messages from the server?

什么是理想的轮询
interval?

What will be the ideal polling interval?

如果你使用非常小的轮询间隔,我的带宽是否会耗尽?我会遇到性能问题吗?

If you use very small polling intervals, will my bandwidth get exhausted? Will I suffer performance problems?


推荐答案

这是一个很老的问题,但我正在寻找类似的答案。我认为渠道API http ://code.google.com/appengine/docs/java/channel/ )更适合此任务。根据我的理解,XMPP很适合与应用程序交互,但不能与其他用户交互。 Channel API通过HttpRequest实现推送通知。我刚刚在这里找到了一个聊天室的例子: https://bitbucket.org/keakon/channelchat

This is a quite old question now, but I was looking for a similar answer. I think the Channel API (http://code.google.com/appengine/docs/java/channel/) is much better suited for the task. For what I understand, XMPP is good to interact with the app, but not with other users. Channel API implement push notifications via HttpRequest. I just found an example of a chat room here: https://bitbucket.org/keakon/channelchat

这篇关于关于appengine的聊天应用程序的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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