Newsgator Forums / NewsGator API / Extras / Disconnect between overview and actual API / Latest Posts

RE: Disconnect between overview and actual API

kmartino — Mon, 28 Nov 2005 17:35:09 GMT

Thanks. That answers my question

RE: Disconnect between overview and actual API

Gordon Weakliem — Fri, 25 Nov 2005 11:13:49 GMT

Well, if you have a set of subscriptions that aren't related to the rest of the subscriptions in your account, and you don't expect them to be related, then I'd say another account is probably the simpler option. Alternatively, you could add the subscription and then remove it from the other locations.

RE: Disconnect between overview and actual API

kmartino — Thu, 24 Nov 2005 07:06:49 GMT

I think I'm confused as well. While I get that the ideas is to have subscriptions synched across locations, I have an app idea I am working on, and I want subscriptions it uses to be distinct from my other locations, which are for personal use, or as the case may have been, for other applications.

Is signing up for an entirely new account the simplest way to achieve this? Or is the process to add a subscription, and remove it from all non-applicable locations?

Does that make sense?

Thanks.

RE: Disconnect between overview and actual API

Gordon Weakliem — Mon, 03 Oct 2005 11:40:14 GMT

OK, I misunderstood the request, I think. I had originally thought that we would support adding subscriptions to only a single location, but it seemed not very useful to me, since you're not really synchronizing subscriptions if the subscription exists in only one location. Now, with Outlook edition, we talk about "private" subscriptions, which are feeds that aren't synchronized at all. I suppose that it could be useful to add a subscription to one location only, but it doesn't make sense for me to have that be the typical case, so I want to understand what you're doing.
Let me elaborate a little on locations. When locations are created, you specify the autoAddSubs attribute (boolean). When you add a new subscription, that subscription is automatically added to every location where autoAddSubs == true. This is what I envisioned the typical situation would be: you want to synchronize your subscription list, so there's an intersection of subscriptions that you read at different locations ("home" and "work" is the canonical distinction). But I think that the intersection is much larger than the reverse; you would normally read a subscription from whatever location you were at. Incidentally, location is an representation of an installed instance of an application. If you're running the same application on 2 different machines (from the user's perspective, clustered servers don't count), those should have different locations, or it will mess up sync.
So, why would you have autoAddSubs='false'? In my case, I have Mobile Edition set up that way, because I have a low-end cell phone plan where I pay by the KB and the odd times I want to read news on my cell, I really only want to see feeds that I really like, because I don't want to chew up costly bandwith on feeds I'm only marginally interested in. So I explicitly add feeds to the Mobile Edition location.
There's another use for locations - you can use them to expose things like a blogroll or headlines. So you can create a "headline" location that just exposes those feeds that you want to have in headlines. There are probably lots of other uses for locations that I haven't thought of - which is exactly the reason why this feedback is valuable!

RE: Disconnect between overview and actual API

Burningbird — Sun, 02 Oct 2005 19:41:40 GMT

Gordon thanks, but I had hoped one could add a new subscription rather than have to add a subscription to a folder, and then grab the id and then use this to add the subscription to a location. This seems awkward.

RE: Disconnect between overview and actual API

Gordon Weakliem — Fri, 30 Sep 2005 10:15:48 GMT

Well, it took longer than I'd hoped, but the AddSubscription and RemoveSubscription functions on Location.asmx will add/remove subscriptions from the named location only.

RE: Disconnect between overview and actual API

Gordon Weakliem — Sun, 18 Sep 2005 21:24:10 GMT

Thanks for the question, the forum is active but is still fairly new. Subscriptions are actually mapped to locations, but the folder structure is reflected in the result of GetSubscriptionsForLocation. Subscription lists are based upon location, but folder structure is global. So the location argument to GSL will affect the result. Unfortunately, at this point there's no way to remove a subscription from a specific location via the API. This was spec'd out originally but never got implemented. I had another customer ask for the same functionality on Friday, so based upon the evident demand, I will try to put this in this week.

Disconnect between overview and actual API

Burningbird — Sun, 18 Sep 2005 17:18:27 GMT

Not sure if this forum is active or not, but here goes.

In your overview for the API, you mention about mapping subscriptions to locations, but in the API, subscriptions are mapped to folders, and as far as I can see, folders aren't mapped to specific locations.

So how does one delete a subscription from a specific location?