The Reader API will be modeled after http://code.google.com/p/pyrfeed/wiki/GoogleReaderAPI
All calls are relative to http://www.asterbox.com/reader/
index.php?fuseaction=logout
parameters: none
description: end the user's session
index.php?fuseaction=sublist
parameters: output=xml/json
description: retrieve the user's subscription list
notes: pass in the user's email and password if there is no session ID (SID)
index.php?fuseaction=feedlist
more info at http://code.google.com/p/pyrfeed/wiki/GoogleReaderAPI
Query for an atom set of items. Sets include feed, label, and state.
States include:
read - A read item will have the state read
kept-unread - Once you've clicked on "keep unread", an item will have the state kept-unread
fresh - When a new item of one of your feeds arrive, it's labeled as fresh. When (need to find what remove fresh label), the fresh label disappear.
starred - When your mark an item with a star, you set it's starred state
broadcast - When your mark an item as being public, you set it's broadcast state
reading-list - All you items are flagged with the reading-list state. To see all your items, just ask for items in the state reading-list
tracking-body-link-used - Set if you ever clicked on a link in the description of the item.
tracking-emailed - Set if you ever emailed the item to someone.
tracking-item-link-used - Set if you ever clicked on a link in the description of the item.
tracking-kept-unread - Set if you ever mark your read item as unread.
The following query modifiers can be used
n - Number of items returns in a set of items (default 20)
client - The default client name
r - By default, items starts now, and go back time. You can change that by specifying this key to the value o (default value is d)
ot - The time (unix time, number of seconds from January 1st, 1970 00:00 UTC) from which to start to get items. Only works for order r=o mode. If the time is older than one month ago, one month ago will be used instead.
ck - current time stamp, probably used as a quick hack to be sure that cache won't be triggered.
xt - another set of items suffix, to be excluded from the query. For exemple, you can query all items from a feed that are not flagged as read. This value start with feed/ or user/, not with !http:// or www
c - a string used for continuation process. Each feed return not all items, but only a certain number of items. You'll find in the atom feed (under the name gr:continuation) a string called continuation. Just add that string as argument for this parameter, and you'll retrieve next items.
Example :
All the 17 first items items from xkcd.com main feed that are not read can be found on the url :
http://www.google.com/reader/atom/feed/http://xkcd.com/rss.xml?n=17&ck=1169900000&xt=user/-/state/com.google/read
image.php
parameters: img_url - the url of the image to be converted, starting with http://
img_max_w - the maximum width of the converted image, in pixels
img_max_h - the maximum height of the converted image, in pixels
img_out_format - JPEG, PNG, or GIF
Friday, June 15, 2007
Sunday, June 10, 2007
Eclipse Error Preverifying Class
I kept getting an error in Eclipse: Error Preverifying Class in JSONArray.java. Sun's website (http://java.sun.com/products/sjwtoolkit/FAQ.html) revealed some useful info regarding the class libraries used in projects:
"If you get this error, you are probably using a class library that was written for Java 2 Platform, Standard Edition (J2SE™ platform). This toolkit supports the development of MIDP applications, which have limited capabilities compared to their J2SE counterparts."
Turns out Eclipse was configured to use an older preverifier and was unaware of java.io.Writer. To fix this, I went to Window > Preferences > J2ME > Preverification > Use specific configuration > Connected Limited Device Configuration (1.1).
"If you get this error, you are probably using a class library that was written for Java 2 Platform, Standard Edition (J2SE™ platform). This toolkit supports the development of MIDP applications, which have limited capabilities compared to their J2SE counterparts."
Turns out Eclipse was configured to use an older preverifier and was unaware of java.io.Writer. To fix this, I went to Window > Preferences > J2ME > Preverification > Use specific configuration > Connected Limited Device Configuration (1.1).
Thursday, May 31, 2007
Friday, April 13, 2007
some open source task management systems.
I have read about kiko.com which is an ajax calendar in
php (open source) .. the site is currently down. but this software couild have
been configured for our use.
php (open source) .. the site is currently down. but this software couild have
been configured for our use.
Moreover i found that the zimbra calendar is open source
but it is written in java
but it is written in java
these calendars are also in java and Ajax based
MOreover i want to tell u that zimbra also has and open
source version
source version
can we do this calendar in java if there is no problem
to the client , we can just configure one of these open source calendars ?
to the client , we can just configure one of these open source calendars ?
pls see this framework
powered by performancing firefox
Sunday, April 8, 2007
j2me authentication problem
There were several issues with google authentication
1) The parameters needed to be encoded , i learnt it from the Java Client LOGIN APi provided by google. THe Java source had to be ported for use in j2me. As some java classes were not available in j2me.
2) Here is the response of a guy from google. Who helped me find the problem
related with j2me.
Please remove the outputStream.flush() call. This call will cause
some j2me-enabled devices to use chunked encoding on the POST. The
ClientLogin service does not seem to like chunked encoding.
3) How he detected the bug
Used the POST being generated by this j2me program and used it
along with 'openssl s_client' and curl to investigate and perform some
trial and error. This led to the discovery of the chunked encoding
problem-- a quick search on the web led to the removal of the flush()
as a solution.
1) The parameters needed to be encoded , i learnt it from the Java Client LOGIN APi provided by google. THe Java source had to be ported for use in j2me. As some java classes were not available in j2me.
2) Here is the response of a guy from google. Who helped me find the problem
related with j2me.
Please remove the outputStream.flush() call. This call will cause
some j2me-enabled devices to use chunked encoding on the POST. The
ClientLogin service does not seem to like chunked encoding.
3) How he detected the bug
Used the POST being generated by this j2me program and used it
along with 'openssl s_client' and curl to investigate and perform some
trial and error. This led to the discovery of the chunked encoding
problem-- a quick search on the web led to the removal of the flush()
as a solution.
Tellme Beta
Supposedly the best app in the mobile search category, they were acquired by MS and only support a few phones by Cingular/ATT and Sprint:
http://beta.tellme.com/content/tellme_by_mobile_overview.php
http://beta.tellme.com/content/tellme_by_mobile_overview.php
Blogging IDE laszlo problem
This is the download link of eclipse IDE with WTP tools and all the required prerequisites
http://download2.bea.com/pub/callisto/wtp153/wtp-all-in-one-sdk-R-1.5.3-win32.zip
THis is the download link of laszlo IDE , this IDE needs to be installed in eclipse by using Software update Manager.
http://www.riftware.com/laszlodev/laszloIDE.zip
THis is The LAszlo Server itself
/>
Instruction on setting up laszlo IDE , pls read the step 7 and 8 carefully :
http://wiki.openlaszlo.org/Installation_Instructions
discussions on the design veiw problem :
http://www.openlaszlo.org/pipermail/laszlo-user/2005-November/002160.html
I am having problems with the design view.
/>
powered by performancing firefox
Subscribe to:
Posts (Atom)