Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Route List - Orchard vs NuGetGallery #159

Closed
BenPhegan opened this Issue Oct 26, 2011 · 5 comments

Comments

Projects
None yet
4 participants

We are running a few instances of the new gallery as well as the old Orchard gallery, and there has been a bit of confusion around the intent regarding the routes.

From nuget.exe, the old Orchard gallery used a /FeedService.svc route for list but the base url for push/delete etc. The new gallery seems to be using /api/feeds/ for the list, and the base (as well as a variety of other urls) for its other functionality.

Realising that we can do whatever we want with these using redirects/rewrites, if we consider this set of urls/routes the interface between all NuGet tooling and a DataServicePackageRepository, is there a spec that states what this will be for each action/verb?

This is particularly important when people are trying to write extensions that they would like to support multiple actions against a single url (for example a list and a push to the same server without providing a separate url for each action).

Contributor

chappoo commented Oct 26, 2011

+1 - this is a source of much confusion. A deployment guide would be very useful with the new gallery. How is the Microsoft redirection implemented?

Member

Haacked commented Nov 1, 2011

There is no redirection going on. We're using routing to point to the endpoint. Routing simply maps the URL to the code that executes, no redirection necessary.

Member

Haacked commented Nov 1, 2011

We'll try and put together a list of the service endpoint URLs.

That would be great. There also appears to be breaking changes between the v1/v2 api/feeds routes, has anyone put together a compatibility matrix (eg 1.4 seems to work with v2, but 1.5 doesnt)? I believe you guys are going with v1 mapped to the same URL as before?

@anurse anurse closed this Feb 22, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment