Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content Negotiation #4

Open
elf-pavlik opened this issue May 6, 2015 · 5 comments
Open

Content Negotiation #4

elf-pavlik opened this issue May 6, 2015 · 5 comments

Comments

@elf-pavlik
Copy link
Member

@akuckartz
Copy link

What is the issue here?!

@elf-pavlik
Copy link
Member Author

Hi @akuckartz

This issue serves just as a place to discuss this topic and document it from perspective of work we do in W3C Social Activity.

We have open issue in WG: ISSUE-24: Do we put requirement on supporting static websites?

AFAIK it also doesn't play well with sites using Content delivery network

@bblfish
Copy link

bblfish commented May 13, 2015

why does "Content-Negotiation" not work with CDN's and why is that not just a bug with those CDNs? Content-Negotiation is pretty core to web architecture. I think it is even part of Roy Fielding's thesis.

As it happens content negotiation is also what helps us work with communities speaking different languages, be it communities represented here with preferences for Turtle, RDF/XML, JSon-LD, or HTML or people with different natural language preferences. It helps work with different devices big or small, as for example images can be sent for the content that is most appropriate for the device....

@elf-pavlik
Copy link
Member Author

why does "Content-Negotiation" not work with CDN's and why is that not just a bug with those CDNs?

http://stackoverflow.com/questions/20242780/which-cdn-solutions-support-caching-with-content-negotiation

we can also do more research, including review of articles like:

@bblfish
Copy link

bblfish commented May 13, 2015

Great, so CloudFront does do content negotiation. Perhaps they can do all of it correctly. If not there is a business opportunity to provide a better service.

Note that if you open issues that are too open ended you'll not know when to close them, and a document can only be ready if all the issues are closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants