Kenyth Zeng's Library tagged client-side → View Popular

Filter:
All
Annotated

06 Jan 10

欢迎使用火狐魔镜 - 火狐中国版

g-fox.cn/...livemargins - Preview

client-side firefox china visualization microformat ideas starred toread

29 Dec 09

node.js

nodejs.org - Preview

javascript server-side client-side toread starred opensource

11 Dec 09

推特中文圈 | bang's blog

blog.webbang.net/863 - Preview

twitter api client-side GAE java china

通过Google AppEngine的Cron功能，每隔一定的时间抓取某一用户的好友存进数据库，存之前判断是否为使用中文的用户。只要从任意一个好友数非零的用户开始抓取，循环下去，就差不多能抓取到所有twitter上的中文用户。对已抓取的则只更新最新消息，这样就形成了“随便看看”
- Google AppEngine的数据库很差，十分差，如下：
  数据库建立后不能增加新栏不能减少栏，必须删除重建才可以。
  Key不能以数字开头，导致我每一个Key前都要增加一个字母。
  查询语句没有like也就算了，连or都没有，服了~导致制作排行榜的标签功能变得困难。
  一次最多只能查询到1000条数据。导致我不知道我已经抓取了多少条数据，排行榜上能显示的也就1000个用户。
  twitter停止source的申请，新应用只有通过OAuth验证才能有“from [myApp]”的字眼，OAuth验证需要经过twitter网站，这对于大陆用户实在不是什么好东西，没有了source，对于宣传和统计很不利。
  本地测试十分慢，是因为本地读取twitter的API十分慢，有时全部传上去在网站上看效果反倒快了，另外Google AppEngine的上传很不方便，就算我只改某一个静态js文件的一个标点，都要整站上传，Eclipse插件也没有提供只更新cron的功能，麻烦。
2 more annotations...
- JAVA写的
- 这种第三方的应用，用户提交id，密码，这个过程会不会被截获啊？安全吗？

开源 php版twitese | bang's blog

blog.webbang.net/1000 - Preview

twitter client-side api opensource php china

随便看看与排行榜是通过GAE版的twitese开放出API进行调用，由于怕原版的twitese流量不足，所以另开了一个GAE重新抓取数据
完整支持手机ucweb浏览，网页上JavaScript的各种操作都留有后路，即使浏览器禁用JavaScript也能正常使用，所以对不太支持JavaScript的手机浏览器也是友好的。

10 Oct 09

FREE PowerPoint Twitter Tools | SAP Web 2.0

www.sapweb20.com/...powerpoint-twitter-tools - Preview

twitter tools client-side PowerPoint SAP ideas innovation

05 Oct 09

ftp clients (Linux Reviews)

linuxreviews.org/...ftp-clients - Preview

ftp client-side tools review

25 Sep 09

Gwibber - GNOME Live!

live.gnome.org/Gwibber - Preview

twitter client-side ubuntu 9.10

Gwibber will be included by default in Ubuntu 9.10

31 Aug 09

Plod: Bitvise Tunnelier: SSH 客户端不错的选择

plod.popoever.com/...001408.html - Preview

tools GFW client-side ssh blog

25 Aug 09

Apps – Laconica

laconi.ca/Apps - Preview

micro-blogging client-side tools

21 Aug 09

Bug #259830 in Gwibber: “Honor gnome proxy setting”

bugs.launchpad.net/...259830 - Preview

bug gnome proxy python twitter client-side

Unfortunately there is a problem upstream with using proxies via urllib2 for secure https connections -- http://bugs.python.org/issue1424152

Therefore, to fix this bug, we would also need to switch to only using http methods when the proxy is enabled.

19 Aug 09

Using the Java Client Library - Google Data APIs - Google Code

code.google.com/...client-java.html - Preview

api java http client-side lib doc gdata Google

04 Aug 09

fftogo - Login

www.fftogo.com/login - Preview

friendfeed mobile api client-side ideas opensource

26 Jul 09

Developing Client-side Code - Google Web Toolkit - Google Code

code.google.com/...FAQ_Client.html - Preview

GWT client-side debug dev javascript java

By default, they are compiled away by the GWT
compiler so do not have any effect in web mode unless you explicitly enable them.

15 Jul 09

FriendFoo

yungsang.com/friendfoo - Preview

friendfeed api client-side

14 Jul 09

dabr - Google Code

code.google.com/dabr - Preview

api twitter php opensource client-side

13 Jul 09

fftogo - Login

fftogo.com/login - Preview

friendfeed api client-side

f2p - a FriendFeed application for mobile

dev.ctor.org/f2p - Preview

friendfeed api mobile client-side

13 Apr 09

Comet (programming) - Wikipedia, the free encyclopedia

en.wikipedia.org/...Comet_(programming) - Preview

ajax comet javascript wikipedia client-side server-side

In web development, Comet is a neologism to describe a web application model in which a long-held HTTP request allows a web server to push data to a browser, without the browser explicitly requesting it.
All these methods rely on features included by default in browsers, such as Javascript, rather than on non-default plugins.^{[original research?]}
14 more annotations...
- In theory, the Comet approach differs from the original model of the web, in which a browser requests a complete web page or chunks of data to update a web page. However in practice, Comet applications typically use Ajax with long polling to detect new information on the server.
- Comet-like applications offer real-time interaction by relying on a persistent HTTP connection
- the HTTP 1.1 specification states that a browser should not have more than 2 simultaneous connections with a web server.
- a distinct hostname for real-time information, which is an alias for the same physical server.
- This invisible IFrame is sent as a chunked block, which implicitly declares it as infinitely long (sometimes called “forever frame”).
- each script tag is executed as it is received.
- a feature called “server push”, which allowed servers to send new versions of an image or HTML page to that browser, as part of a multipart HTTP response (see History section, below), using the content type multipart/x-mixed-replace.
- On the server side, each message is encoded as a separate portion of the multipart response, and on the client, the callback function provided to the XHR onreadystatechange function will be called as each message arrives. This functionality is only included in Gecko-based browsers, though there is discussion of adding it to Webkit.^[10]
- it is also possible to generate a custom data format for an XHR response, and parse out each event using browser-side JavaScript,
- long polling requires the client to poll the server for an event (or set of events). The browser makes an Ajax-style request to the server, which is kept open until the server has new data to send to the browser, which is sent to the browser in a complete response. The browser initiates a new long polling request in order to obtain subsequent events.
- While any Comet transport can be made to work across subdomains, none of the above transports can be used across different second-level domains (SLDs)
- script tags can be pointed at any URI, and JavaScript code in the response will be executed in the current HTML document.
- The BOSH protocol by the XMPP standards foundation. It emulates a bidirectional stream between browser and server by using multiple synchronous HTTP connections.
- The JSONRequest object, proposed by Douglas Crockford, would be an alternative to the XHR object.^[22]