pleasedressme - Project Hosting on Google Code

Older Jan 18, 2009 issue 2 (Certain tags return unknown error from search) commented on by gregg.hilferding - For pagination via APIs, it's often really helpful to get some data regarding how many results are available for any particular query. You could look at the "Example Response" for Flickr's API for one way of doing this: http://www.flickr.com/services/api/flickr.photos.search.html If you don't do that, then any developer who wants to provide pagination through to their end user would need to essentially page through the entire result set for any given query until they hit an error page (or a page with less than the `limit` number of results) just so they know whether or not to show a "next" button or to be able show "showing x of xx results" Not ideal, particularly because it's a lot of extra server hits for you. For pagination via APIs, it's often really helpful to get some data regarding how many results are available for any particular query. You could look at the "Example Response" for Flickr's API for one way of doing this: http://www.flickr.com/services/api/flickr.photos.search.html If you don't do that, then any developer who wants to provide pagination through to their end user would need to essentially page through the entire result set for any given query until they hit an error page (or a page with less than the `limit` number of results) just so they know whether or not to show a "next" button or to be able show "showing x of xx results" Not ideal, particularly because it's a lot of extra server hits for you. Jan 18, 2009 issue 2 (Certain tags return unknown error from search) commented on by gregg.hilferding - For pagination via APIs, it's often really helpful to get some data regarding how many results are available for any particular query. You could look at <a href="http://www.flickr.com/services/api/flickr.photos.search.html">Flickr's API</a> for one method of doing this. If you don't do that, then any developer who wants to provide pagination through to their end user would need to essentially page through the entire result set for any given query until they hit an error page (or a page with less than the `limit` number of results) just so they know whether or not to show a "next" button or to be able show "showing x of xx results" Not ideal, particularly because it's a lot of extra server hits for you. For pagination via APIs, it's often really helpful to get some data regarding how many results are available for any particular query. You could look at <a href="http://www.flickr.com/services/api/flickr.photos.search.html">Flickr's API</a> for one method of doing this. If you don't do that, then any developer who wants to provide pagination through to their end user would need to essentially page through the entire result set for any given query until they hit an error page (or a page with less than the `limit` number of results) just so they know whether or not to show a "next" button or to be able show "showing x of xx results" Not ideal, particularly because it's a lot of extra server hits for you. Dec 09, 2008 issue 2 (Certain tags return unknown error from search) Status changed by jstump - Okay, this is fixed. Now you can use the `start` and `limit` arguments to paginate through results (they work just like MySQL's LIMIT clause). Default `limit` is 40 shirts. Try ?start=0, ?start=40, ?start=80, etc. Status: Fixed Okay, this is fixed. Now you can use the `start` and `limit` arguments to paginate through results (they work just like MySQL's LIMIT clause). Default `limit` is 40 shirts. Try ?start=0, ?start=40, ?start=80, etc. Status: Fixed Dec 09, 2008 issue 1 (add price to search) Status changed by jstump - Sorry for the slow response. Price was added a while ago. Color is included in the tags. Status: Fixed Sorry for the slow response. Price was added a while ago. Color is included in the tags. Status: Fixed Dec 09, 2008 issue 2 (Certain tags return unknown error from search) Status changed by jstump - Ah, I need to add pagination to the API it seems. I'll look into this soon. Sorry! Status: Accepted Ah, I need to add pagination to the API it seems. I'll look into this soon. Sorry! Status: Accepted Nov 04, 2008 issue 2 (Certain tags return unknown error from search) reported by James.L.Williams - What steps will reproduce the problem? 1. Call http://pleasedress.me/api/1.0/shirts/search.xml?q=green via the api or navigate to it in a browser 2. Parse results What is the expected output? It should return a list of shirts with the tag green. What do you see instead? <result> <error message="Unknown fatal error" code="100"/> </result> What version of the product are you using? On what operating system? 1.0/ Linux(FF and Iceweasel), Google Android Please provide any additional information below. What steps will reproduce the problem? 1. Call http://pleasedress.me/api/1.0/shirts/search.xml?q=green via the api or navigate to it in a browser 2. Parse results What is the expected output? It should return a list of shirts with the tag green. What do you see instead? <result> <error message="Unknown fatal error" code="100"/> </result> What version of the product are you using? On what operating system? 1.0/ Linux(FF and Iceweasel), Google Android Please provide any additional information below. Sep 08, 2008 issue 1 (add price to search) reported by italiano40 - it would be great if you could add to the search xml to show price and color it would be great if you could add to the search xml to show price and color Sep 07, 2008 r6 (Recreated proper tag. ) committed by jstump - Recreated proper tag. Recreated proper tag. Sep 07, 2008 r5 (Added 0.0.1 tag. ) committed by jstump - Added 0.0.1 tag. Added 0.0.1 tag. Sep 07, 2008 r4 (Fixed package.xml up for 0.0.1 release. ) committed by jstump - Fixed package.xml up for 0.0.1 release. Fixed package.xml up for 0.0.1 release. Sep 07, 2008 r3 (Added Tags API group, created a package.xml and cleaned up c...) committed by jstump - Added Tags API group, created a package.xml and cleaned up code to be PEAR CS compliant. Added Tags API group, created a package.xml and cleaned up code to be PEAR CS compliant. Sep 06, 2008 r2 (Added rough code for the first version. ) committed by jstump - Added rough code for the first version. Added rough code for the first version. Sep 06, 2008 Project pleasedressme created by jstump - PleaseDressMe Tshirt Search Engine API PleaseDressMe Tshirt Search Engine API

issue 2 (Certain tags return unknown error from search) commented on by gregg.hilferding - For pagination via APIs, it's often really helpful to get some data regarding how many results are available for any particular query. You could look at the "Example Response" for Flickr's API for one way of doing this: http://www.flickr.com/services/api/flickr.photos.search.html If you don't do that, then any developer who wants to provide pagination through to their end user would need to essentially page through the entire result set for any given query until they hit an error page (or a page with less than the `limit` number of results) just so they know whether or not to show a "next" button or to be able show "showing x of xx results" Not ideal, particularly because it's a lot of extra server hits for you.

For pagination via APIs, it's often really helpful to get some data regarding how many results are available for any particular query. You could look at the "Example Response" for Flickr's API for one way of doing this: http://www.flickr.com/services/api/flickr.photos.search.html If you don't do that, then any developer who wants to provide pagination through to their end user would need to essentially page through the entire result set for any given query until they hit an error page (or a page with less than the `limit` number of results) just so they know whether or not to show a "next" button or to be able show "showing x of xx results" Not ideal, particularly because it's a lot of extra server hits for you.

Older