Re: [Erlyaws-list] Content Negotiation

[Vlad D. <vla...@ho...>]

> What is needed is a general way to tag URIs which may be served by
> the yaws server with optional metainformation.  This information
> would be used to create entity headers (e.g. Content-Language) for
> simple GETs as well as drive the new content negotiation functionality.

Hi,

I apologize if I am going to express a silly idea, this isn't my best area 
of expertise...

Wouldn't it be possible to have the URI point to a file that contains both 
headers and content?

I was looking the other week at StringTemplate (www.stringtemplate.org), 
which is a cool template engine IMHO, and wondered if it couldn't be used 
with yaws - the reason being that I think the "<erl> out()-> stuff end. 
</erl>" notation is awkward. Better to have a simple template that 
encompasses even headers (when needed) and fully separate presentation from 
the data source.

If it looks interesting, I have started to implement something similar in 
Erlang. I don't remember why I didn't finish it ;-)

regards,
Vlad