Kenyth Zeng's Library tagged api → View Popular

Filter:
All
Annotated

29 Dec 09

- python-twitter by DeWitt Clinton. This library provides a pure Python interface for the Twitter API.
- python-twyt by Andrew Price. BSD licensed Twitter API interface library and command line client.
- twitty-twister by Dustin Sallings. A Twisted interface to Twitter.

24 Dec 09

GeoAPI.com - location infrastructure, GIS, and geo-location services

www.geoapi.com - Preview

api geolocation ideas starred toread

16 Dec 09

Python: module twitter

static.unto.net/...twitter.html - Preview

python twitter api doc opensource

14 Dec 09

Famous Followers Scanner

should be combined with the report spam app

famousfollowers.appspot.com - Preview

twitter api ideas

11 Dec 09

Twitter4J - A Java library for the Twitter API

yusuke.homeip.net/...index.html - Preview

twitter api java opensource

推特中文圈 | 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的手机浏览器也是友好的。

02 Dec 09

China Telecom Launches New Open Development Platform | Marbridge Consulting - China Wireless News

www.marbridgeconsulting.com/..._new_open_development_platform - Preview

api OpenWeb china China Telecom news

The "Open Abilities" initiative is composed of two major parts: the "Open Abilities" platform and the E-Surfing applications factory.
Some core services, like SMS, IVR, voice communication, and location-based services will be opened to regular developers via the platform. Developers will be able to apply for and employ such resources in their open applications.
1 more annotations...
- The application factory will provide developers with a broad collection of freely-available APIs from a large number of internet providers.

30 Nov 09

twfav Help Center

docs.twfav.com - Preview

twitter api ideas

Location-aware mobile web apps using Google Maps v3 + geolocation | mobile geo social

hitching.net/...ing-google-maps-v3-geolocation - Preview

twitter api geolocation Google Maps blog ideas toread

16 Nov 09

Trendsmap - Real-time local Twitter trends

trendsmap.com - Preview

trends twitter api ideas

07 Nov 09

tweetfeel Twitter Sentiment - Real-time Twitter search with feelings towards your favorite brand, celebrity or anything else. (Tweet Feel)

www.tweetfeel.com - Preview

twitter api ideas statistics analysis

04 Nov 09

Discover the secrets of the Java Serialization API

www.j2ee.me/...serialization - Preview

java serialization starred api article persistence

That means we could easily transfer a flattened object across a network wire and have it be rebuilt on the other side!
In other words, the object's class file and methods are not saved; only the object's state is saved.
15 more annotations...
- the class file must be accessible from the system in which the restoration occurs
- what if we have a class that contains an instance of Thread? In that case, can we ever persist objects of that type? The answer is yes, as long as we tell the serialization mechanism our intentions by marking our class's Thread object as transient.
- The bottom line: you must mark transient any field that
  either cannot be serialized or any field you do not want serialized.
- That does not make for a seamless mechanism,
  something the Java Serialization API promises developers.
- developers can enhance the normal process by
  providing two methods inside their class files. Those methods are:
  
  private void writeObject(ObjectOutputStream out) throws IOException;
  private void readObject(ObjectInputStream in) throws IOException, ClassNotFoundException;
  
  Notice that both methods are (and must be) declared private, proving
  that neither method is inherited and overridden or overloaded.
- 230   private void readObject(ObjectInputStream in) throws IOException, ClassNotFoundException
  
  240   {
  
  250     // our "pseudo-constructor"
  
  260     in.defaultReadObject();
  
  270     // now we are a "live" object again, so let's run rebuild and start
  
  280     startAnimation();
  
  290
  
  300   }
- Those methods work because the call to ObjectOutputStream.writeObject()
  kicks off the serialization protocol. First, the object is checked to ensure it
  implements Serializable and then it is checked to see whether
  either of those private methods are provided. If they are provided, the
  stream class is passed as the parameter, giving the code control over its usage.
- Encryption could be added to the output and decryption
  to the input (note that the bytes are written and read in cleartext with no
  obfuscation at all).
- , you can once again use the private methods to just throw the
  NotSerializableException.
- you can implement Externalizable,
- That means that if the state of the written
  object is written and then written again, the new state will not be saved!
- That flattened object sits in the file system for some
  time.
- because all persistent-capable
  classes are automatically given a unique identifier. If the identifier of the
  class does not equal the identifier of the flattened object, the exception will
  be thrown.
- If you wish to control versioning, you simply have to provide the serialVersionUID
  field manually and ensure it is always the same, no matter what changes you make to
  the classfile.
- serialver Baz

PayPal X Developer Network

www.x.com/index.jspa - Preview

paypal ecommerce OpenWeb api payment

03 Nov 09

PackageAdmin (OSGi Service Platform Release 4 Version 4.1)

how to eliminate class loader memory leak when uninstalling a bundle: call the refreshPackages method.

www.osgi.org/...PackageAdmin.html - Preview

OSGi api javadoc package classloader memory leak

If no bundles are specified, this method will update or remove any
packages exported by any bundles that were previously updated or
uninstalled since the last call to this method.
One permissible implementation is to stop and restart the Framework.
3 more annotations...
- Add to the
  graph any bundle that is wired to a package that is currently exported by
  a bundle in the graph.
- Each bundle in the graph that is in the ACTIVE state
  will be stopped as described in the Bundle.stop method.
- The effect of this step is that bundles in the graph are no longer
  RESOLVED.