<?xml version="1.0" encoding="windows-1252"?>
<node id="1014955" title="Re: Do you hide .pl extension on web pages?" created="2013-01-23 11:36:26" updated="2013-01-23 11:36:26">
<type id="11">
note</type>
<author id="272364">
MidLifeXis</author>
<data>
<field name="doctext">
&lt;P&gt;
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).
&lt;/P&gt;
&lt;p&gt;Allows me to do things like &lt;c&gt;http://example.com/api/parts/&lt;/c&gt; instead of &lt;c&gt;http://example.com/vendor_endpoint/getAllParts.cgi....&lt;/c&gt;.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div class="pmsig"&gt;&lt;div class="pmsig-272364"&gt;
&lt;p&gt;--MidLifeXis&lt;/p&gt;

&lt;/div&gt;&lt;/div&gt;</field>
<field name="root_node">
1014942</field>
<field name="parent_node">
1014942</field>
</data>
</node>
