谷歌+深入的社交网络

发布于 2024-11-18 12:50:00 字数 107 浏览 2 评论 0原文

Google+ 使用什么语言编写(服务器端)?

例如,Facebook 是用 Php 编写并用 C++ 编译的。

编辑:他们如何设法将谷歌搜索的+1链接到您的个人资料?

In what language is Google+ written (server side) ?

Facebook is written in Php and compiled in C++ for example.

Edit: how do they manage to link the +1 from google search, to your profile ?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

棒棒糖 2024-11-25 12:50:00

服务器将自己标识为“GSE”:“Google Servlet Engine”。开源" minigse”可用

所以它很可能是一个java前端服务器堆栈。

但谁又关心这个呢?客户端才是最重要的,Google 有 2 个强大的 Web 应用工具:closure 和 gwt。给定一个 DOM 变量“closure_uid_[...]”,我会说闭包正在使用中。某处。

我们还能看到什么?
- 图像由“googleusercontent”和一个自称为 fife 的网络服务器提供
- - 大量缓存。更新用户图像需要一些时间
- GoogleTalk“按原样”集成。几乎没有什么太特别的。集成非常像gmail。
- 仍然使用Flash(聊天音频通知)
- 内容通过“转发”复制到新流
- - 这意味着每个用户都有一个复制内容的个人流
(在谷歌退休“马克·扎克伯格”假帐户时发现这一点:转发的内容是实时的,名称错误{用户被重命名为“假扎克伯格”,但发帖仍为“马克·扎克伯格”})

+1点击是路由通过顶部栏:gbar.pw.clk(this);

现在,顶栏可以与 plusone 核心对话:两者都知道您的登录信息,并且两个服务相互信任。为此确实没有什么特别要做的。

更新

这是 Android 应用程序的一个片段:

I/RealTimeChat(30274): Processing stream features

因此他们很可能将其构建在 XMPP 基础设施(如 gtalk 和 wave)之上。此外,一位开发人员谈到了 Circles 编辑器和 JS 编码。因此 Clojure 应该被视为已确认。

The server identifies itself als "GSE": "Google Servlet Engine". An open source "minigse" is available

So it's likely a java frontend server stack.

But who cares about that anyway? The client is what matters, and google has 2 powerfull tools for web apps: closure and gwt. Given a DOM variable "closure_uid_[...]" I'd say closure is in use. Somewhere.

What else can we see?
- Images are served from "googleusercontent" and a webserver that calls itself fife
- - Heavy caching. It takes some time until a user image is updated
- GoogleTalk is integrated "as-is". Barely anything too special. Integration is very gmail like.
- Flash is still used (chat audio notifications)
- Content is duplicated to the new stream on "reshare"
- - This means that every user has a personal stream where content is copied
(Found this while google retired the "Mark Zuckerberg" fake account: reshared content was live, with wrong name {The user was renamed to "Fake Zuckerberg", but the postings stayed as "Mark Zuckerberg"})

The +1 click is routet through the top bar: gbar.pw.clk(this);

Now the topbar could just talk with the plusone core: both know your login and both services trust each other. There is really nothing special to do for this.

UPDATE

Here is a snippet from the Android app:

I/RealTimeChat(30274): Processing stream features

So they've most likely build it on top of their XMPP infrastructure (like gtalk and wave). Furthermore one dev talked about the circles editor and about JS coding. Thus clojure should be regarded as confirmed.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文