Hi David, <div class="gmail_quote">On Fri, Aug 31, 2012 at 9:56 AM, 梁辰晔 <<a href="mailto:liangchenye@gmail.com" target="_blank">liangchenye@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi, I think it will bring confusion to add 'afterdate'. For example, list with page=1, pagesize=10, afterdate = yesterday, search=foo. Your mean: the server should 1) search item=foo 2) find page=1&pagesize=10 3) find afterdate item But the first impression (for me): the server should 1) search item=foo & find afterdate item 2) find page=1&pagesize=10 </blockquote><div> I hope I understand your point correctly, but please feel free to correct me if I am mistaken. :-) I believe the specific search method on the server side is better left to the servers. If we decide about the priority then we may provide slower or faster (or not even possible at times) functionality in certain cases. It depends on the specific instance what the optimized way is for collecting the data output. As from OCS specification documentation point of view, the page and pagesize arguments are always the last parameters in the parameter list as far as I see. Hope, that would somewhat help with dismissing your confusion. </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> How about add another URL to work with it <li>URL Arguments: ids - Ids of the requested content ids seperated by "x". </li> </blockquote><div> Unfortunately, we do not know the ids for the entries that were added or modified. We would need a separate query for getting the updated items, but that requires a query (i.e. bit slower from the client point of view), and that would not allow "advanced" search either what we may need if we would like to get the updated for a filtered list. Laszlo </div></div>