Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query Service: Get data from partsregistry.org #2

Closed
2 tasks done
mef51 opened this issue Jun 4, 2013 · 2 comments
Closed
2 tasks done

Query Service: Get data from partsregistry.org #2

mef51 opened this issue Jun 4, 2013 · 2 comments
Assignees
Labels

Comments

@mef51
Copy link
Member

mef51 commented Jun 4, 2013

We need good ways of accessing data from partsregistry.org.

http://partsregistry.org/Registry_API
http://igempartview.appspot.com/api.jsp

  • Expose access to the 4 search boxes on http://partsregistry.org/cgi/partsdb/search.cgi
  • Parse response from partsregistry. Currently they just give back an HTML page, not data... Plan is to grab the parts returned by the search and then query the XML API for more specific information.
@mef51
Copy link
Member Author

mef51 commented Jun 25, 2013

We were discussing about having this all on the client-side. I liked this idea.

I was trying to make ajax requests to partsregistry.org from the client side (all the code in the assets/js folder) but was getting errors from something called Access-Control-Allow-Origin. This has something to do with CORS. I was looking around and it seemed like partsregistry itself would have to allow us to make these ajax requests.

Since that wasn't working I moved the searching code from the client to the server (see all the code that is not in assets/js, namely brickSearchService.coffee) and was able to make requests to partsregistry from there.

I'm not sure why we can make requests to partsregistry from the server but not from the client. They're both "cross-domain" and outside of partsregistry. If anyone can answer this I'll give you a cookie.

The way it is now, the client side will make requests to our server, which will then do the actual search request to partsregistry, and then pass the data back to the client.

@mef51
Copy link
Member Author

mef51 commented Jul 30, 2013

The search is implemented by #8

@mef51 mef51 closed this as completed Jul 30, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant