<p>So if you have a RIA version (Silverlight or Flash) and a standard HTML version (or AJAX even), should you have the same URL for both, or is it ok to have a different one for the RIA app and just redirect accordingly?</p>

<p>So, for instance, if you have a site (<a href="http://example.com" rel="nofollow noreferrer">http://example.com</a>), is it ok to have the about page URL for the RIA app be <a href="http://example.com/#/about" rel="nofollow noreferrer">http://example.com/#/about</a> and the html be <a href="http://example.com/about" rel="nofollow noreferrer">http://example.com/about</a>? Does it matter? </p>

<p>Of course if you take the route with different URLs you will need to map between them. </p>

[{'answer_id': 77441, 'author': 'UnkwnTech', 'author_id': 115, 'author_profile': 'https://Stackoverflow.com/users/115', 'pm_score': 2, 'selected': False, 'text': "<p>It's perfectly acceptable to use 2 different link formats.  If 2 users are not seeing the same content why should they be at the same URL.</p>\n"}, {'answer_id': 78245, 'author': 'Bryant', 'author_id': 10893, 'author_profile': 'https://Stackoverflow.com/users/10893', 'pm_score': 1, 'selected': False, 'text': "<p>I guess what I really need here is not a Question/Answer format but some kind of poll. While I agree (and accepted) that because they are getting two different views of the same content, that different urls are ok, but I'm thinking more of sharing these urls out. </p>\n\n<p>Thanks for the reply though!</p>\n"}, {'answer_id': 78378, 'author': 'Ian Dickinson', 'author_id': 6716, 'author_profile': 'https://Stackoverflow.com/users/6716', 'pm_score': 3, 'selected': True, 'text': '<p>The URLs of your pages denote the identity of the content. In my view, if the content is the same but the presentation varies (i.e RIA vs. HTML), then the URL should be the same and you should use some other mechanism to select between the different presentation forms. Choices of other mechanisms include cookies, content negotiation, session identifiers or, if your users are identified, a persistent user preferences model. Even using a URL argument would at least keep the root of the URL consistent (e.g. <code>http://your.si.te/foobar</code> vs. <code>http://your.si.te/foobar?view=plain</code>)</p>\n\n<p>If the content of the two presentations differs in some meaningful way, then you should make that difference meaningful in the URL. Exploiting the presence or absence of #, and other such hacks, would be a mistake in my view.</p>\n\n<p>Try to pick URL\'s that do not change over time: so-called <a href="http://www.w3.org/Provider/Style/URI" rel="nofollow noreferrer" title="cool URL&#39;s">cool URL\'s</a>. This will aide the long-term usefulness of your site to your users: consider what happens if they come back to a bookmarked page in a year\'s time. Consistency will also help you to get a better critical mass of links or reviews of your site in <a href="http://del.icio.us" rel="nofollow noreferrer">del.icio.us</a> and similar bookmarking/review sites.</p>\n\n<p>Ian</p>\n'}]
['https://Stackoverflow.com/questions/77428', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/10893/']