Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339612 - should we switch from # to #!
Summary: should we switch from # to #!
Status: RESOLVED WONTFIX
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-10 17:33 EST by Susan McCourt CLA
Modified: 2011-10-27 15:42 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Susan McCourt CLA 2011-03-10 17:33:27 EST 
Forgetting about the broader issues of Web Site architecture, it seems like we should be using hash bang instead of just hash.
Comment 1 Boris Bokowski CLA 2011-03-10 19:47:33 EST 
This would require following the spec that Google put forward for using hashbang instead of hash.
Comment 2 Simon Kaegi CLA 2011-03-10 22:05:03 EST 
We can talk more about this but I'm not so sure. You typically use hash-bang for URI to the real content so that search engines can recognize the difference between pages that unique "internal" content vs. a sub-section of a resource.

In our case we don't actually host the content so it's not an internal address to something otherwise not viewable as other than relative case we use the full URI.
Comment 3 John Arthorne CLA 2011-10-27 15:42:27 EDT 
I don't think we'd care about an external search engine indexing your workspace anyway - it's inevitably going to be stale.