hunchentoot serving manifest files, ie. .appcache files.

[Faruk S. Can]

i am also scanning hunchentoot documentation.
i have found about outgoing headers,
the accessor header-out  and setf of it creates a new one if not exists.
maybe sent content type header can be setf ed by this at the beginnig of
the lisp function
that has been dispatched to the url. by url I mean script mentioning it as
eventSource("url") in html5 document.
same for cache-control header.

Is there any inside thing in the implementation of server that shuld be
changed?
Am I naively thinking above not regarding implementation of the server?


On Fri, Feb 28, 2014 at 11:09 PM, Faruk S. Can <farukscan at gmail.com> wrote:

> I have read in w3schools about usage of server sent events in html5.
> it says:
>
>    - Set the "Content-Type" header to "text/event-stream"
>    - Specify that the page should not cache
>    - Output the data to send (*Always* start with "data: ")
>
> that is in echo line in php code as echo "data: The server time is:
> {$time}\n\n";
>
>    - Flush the output data back to the web page
>
> http://www.w3schools.com/html/html5_serversentevents.asp
> examples here are in php for server side. i am using hunchentoot on common
> lisp.
>
>
>
> On Fri, Feb 28, 2014 at 10:27 PM, Faruk S. Can <farukscan at gmail.com>wrote:
>
>> I
>>   have another question about hunchentoot. Is it possible to use server
>> sent events with hunchentoot, like other html5 improvements mentioned in
>> w3schools-html5 such as app cache, local storage, session storage? as that
>> one related to and depend on the server side support.
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/tbnl-devel/attachments/20140228/540ee547/attachment.html>