Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 339612

Summary:	should we switch from # to #!
Product:	[ECD] Orion	Reporter:	Susan McCourt <susan>
Component:	Client	Assignee:	Project Inbox <orion.client-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	bokowski, simon_kaegi
Version:	0.2
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Susan McCourt

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

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

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

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.