﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Newsgator Forums / NewsGator API / Extras  / REST API - Question re: response to call to PostItem.aspx / Latest Posts</title><generator>InstantForum.NET v4.1.4</generator><description>Newsgator Forums</description><link>http://forum.newsgator.com/</link><webMaster>info@newsgator.com</webMaster><lastBuildDate>Wed, 07 Jan 2009 10:36:40 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: REST API - Question re: response to call to PostItem.aspx</title><link>http://forum.newsgator.com/Topic29900-8-1.aspx</link><description>This has slipped due to higher priorities, but let me take a look and see where we are at with the endpoint.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rob</description><pubDate>Wed, 23 Jul 2008 15:51:13 GMT</pubDate><dc:creator>Rob Ponti</dc:creator></item><item><title>RE: REST API - Question re: response to call to PostItem.aspx</title><link>http://forum.newsgator.com/Topic29900-8-1.aspx</link><description>Was the UpdatePostMetaData call ever finalized? It still says TBD in the docs. I'd like to be able to set the flagged state using the REST API.</description><pubDate>Thu, 17 Jul 2008 18:15:10 GMT</pubDate><dc:creator>vigilsolace</dc:creator></item><item><title>RE: REST API - Question re: response to call to PostItem.aspx</title><link>http://forum.newsgator.com/Topic29900-8-1.aspx</link><description>Rob,&lt;br&gt;  That's great news, thanks! Please let me know as soon as you're ready; I'll be glad to help test it out.&lt;br&gt;&lt;br&gt;B</description><pubDate>Sat, 20 Oct 2007 09:11:45 GMT</pubDate><dc:creator>BenGottlieb</dc:creator></item><item><title>RE: REST API - Question re: response to call to PostItem.aspx</title><link>http://forum.newsgator.com/Topic29900-8-1.aspx</link><description>Hi Ben, &lt;P&gt;In response to both yours and Dan's inquires, we have been working to implement the equivalent of the SOAP call PostItem.asmx/UpdatePostMetaData into the REST API.  UpdatePostMetaData handles all of the read/flag state changes for a given feed/post.  It definitely uses a sync token obtained from a previous Subscription.aspx call to keep results to a bare minimum.&lt;/P&gt;&lt;P&gt;We hope to have a working version available to you for use in the coming weeks, so hang on! :)&lt;/P&gt;&lt;P&gt;-Rob&lt;P&gt;NewsGator QA</description><pubDate>Tue, 16 Oct 2007 13:22:04 GMT</pubDate><dc:creator>Rob Ponti</dc:creator></item><item><title>RE: REST API - Question re: response to call to PostItem.aspx</title><link>http://forum.newsgator.com/Topic29900-8-1.aspx</link><description>I'm also having a problem with the PostItem call. I working in a low-bandwidth, low-memory environment, so parsing 600k of return data each time a call is made is not feasible (really, ANY call that returns 600k is a no-go for me). I'm trying to figure out how to work the ng:token value into the call. &lt;br&gt;&lt;br&gt;My app follows this basic sequence:&lt;br&gt;&lt;br&gt;- Call Subscription.aspx/&lt;locationname&gt; to fetch a list of feeds&lt;br&gt;- Call Feed.aspx/&lt;feedID&gt; for each feed to get a list of posts for that feed&lt;br&gt;- When a group of posts has been marked read, or a timer fires, call PostItem.aspx to update the server with their read status&lt;br&gt;&lt;br&gt;I've tried passing ?token=reallyLongTokenString with the PostItem call (using both the token returned by Subscription.aspx and the one from Feed.aspx), but neither one seems to effect the output. Any suggestions?&lt;br&gt;&lt;br&gt;Thanks!&lt;br&gt;&lt;br&gt;B</description><pubDate>Mon, 15 Oct 2007 16:10:39 GMT</pubDate><dc:creator>BenGottlieb</dc:creator></item><item><title>RE: REST API - Question re: response to call to PostItem.aspx</title><link>http://forum.newsgator.com/Topic29900-8-1.aspx</link><description>Hey Dan,&lt;/P&gt;&lt;P&gt;One of the API guys wants to go over this with you, we may have a beta API that you can use which could work better for you ;). Can you shoot an email to &lt;A href="mailto:support@newsgator.com"&gt;NewsGator Support&lt;/A&gt; - I'll make sure it gets to the right guys.</description><pubDate>Mon, 16 Jul 2007 16:49:34 GMT</pubDate><dc:creator>Jonathon McDougall</dc:creator></item><item><title>REST API - Question re: response to call to PostItem.aspx</title><link>http://forum.newsgator.com/Topic29900-8-1.aspx</link><description>Following up on my [url=http://forum.newsgator.com/Topic29865-8-1.aspx]previous post[/url], I see that each call to PostItem.aspx to submit post states results in a reponse with "the current state of all posts in any feed where read state has changed since the last sync."&lt;br&gt;&lt;br&gt;This means that for every call, I receive a response of over 700kB, which takes anywhere from 1.5 to 4.5 seconds. That's a lot of bandwidth and time for a call that happens so frequently (in my case, to mark a post or group of posts as read).&lt;br&gt;&lt;br&gt;I am not currently using any of the information in this response, so I'd love it if you could add a flag that would allow me to specify that I want the server to limit the response body to a simple "OK" or error, something like:&lt;br&gt;&lt;br&gt;[quote]Request Format: application/x-www-form-urlencoded&lt;br&gt;[code]"loc=&amp;lt;locationName&amp;gt;&amp;r=&amp;lt;postId&amp;gt;&amp;u=&amp;lt;postId&amp;gt;&amp;d=&amp;lt;postId&amp;gt;&amp;q=&amp;lt;0|1&amp;gt;"[/code]&lt;br&gt;          o loc – specify the location name to submit the read state changes (OPTIONAL)&lt;br&gt;          o r – mark a post read (can be specified multiple times)&lt;br&gt;          o u – mark a post uread (can be specified multiple times)&lt;br&gt;          o d - mark a post deleted (can be specified multiple times)&lt;br&gt;          o q - specify 1 to request a "quiet" reponse from the server (i.e., omit the current state of all posts since the last sync)[/quote]&lt;br&gt;&lt;br&gt;Also, the draft of the new REST API documentation I have implies that this list of current posts should be limited to those that have changed since the last sync. However, I don't see how I can indicate when that happened. Should I add the last sync token from the location's OPML?&lt;br&gt;&lt;br&gt;Thanks, all.</description><pubDate>Sun, 15 Jul 2007 14:31:56 GMT</pubDate><dc:creator>Dan MacTough</dc:creator></item></channel></rss>