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

Other URI Template implementations #2

Open
rodneyrehm opened this issue Aug 11, 2012 · 6 comments
Open

Other URI Template implementations #2

rodneyrehm opened this issue Aug 11, 2012 · 6 comments

Comments

@rodneyrehm
Copy link

Hey Franz,

nice work! Of course I only found your implementation hours after publishing my own. Just wanted to point you to uri-templates by Marc Portier and my URITemplate. I did a little performance testing - your implementation is clearly in the lead. grats!

How are your plans regarding the extraction of values through templates coming?

@fxa
Copy link
Owner

fxa commented Aug 20, 2012

The extraction is not prio 1, first I have to make the bug fixes -- Mark Nottingham added some new test cases to https://github.com/uri-templates/uritemplate-test and my implementation fails that new tests.
Of course only a subset of templates are extractable, and it is no easy job to determine, which are.
So I will start with very simple one and then extend, when needed.
e.g. I will start with only complete path segments ("/fixed/{segmentVar}/anotherfixed") and disallow explosions ("*")

By the way, I can completely understand your thoughts about the rfc. All your points. And I have some amendments:
the encodings of the uri template rfc do not match the encodings of the uri rfc. For example, the '@' has to be encoeded to %40 for {?x} but is allowed in uris like http://www.example.com?a=@
But the uri rfc is so complex and there is no test case project...

By the way, you are from germany, too. Why are we talking Englisch?

@rodneyrehm
Copy link
Author

So I will start with very simple one and then extend, when needed.

I was considering trashing my own implementation and simply referencing yours in URI.js. Which would only make sense if yours allowed extraction before I could get around to implementing it.

By the way, you are from germany, too. Why are we talking Englisch?

Yes, I'm from Germany. We are speaking English because this is the OS world and other may want to chime in. :)

@Almad
Copy link

Almad commented Aug 21, 2012

+1 for extraction support ,)

@mb21
Copy link

mb21 commented Jun 30, 2014

@rodneyrehm You didn't get around to implementing extraction, right? geraintluff/uri-templates seems to do the job or do you know of a better implementation?

@rodneyrehm
Copy link
Author

I've not implemented this in URI.js yet. I'm rather playing with the idea of binding an external library and throwing out my own implementation. But I haven't looked at the problem in a while. Feel free to open another issue over at URI.js

@fxa
Copy link
Owner

fxa commented Jul 1, 2014

@mb21 You are right, I did not manage to implement extraction, yet. I saw the implementation you mentioned, but I did not test it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants