I tend to abstract the endpoint, named as what I want it to do, not named as what does it. I also use mod_rewrite for applications not able to handle the rewrite within (vendor CGI, for example).
Allows me to do things like http://example.com/api/parts/ instead of http://example.com/vendor_endpoint/getAllParts.cgi.....
If our vendor changes, their implementation changes, they have a hardcoded endpoint (.../cgi-bin/..., for example), or we add a layer in front of the vendor's implementation (say for another parts database), I am able to add that into the system without the client application (or the user) knowing the difference. It does require some planning and maintenance on your endpoints. I use it because it isolates our API from the implementation of our API.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||