Mackram wrote:
>
> I am not sure Leslie what i am missing but I am unable to see what is
> requested or to debug the flow of the code. The trace shows something
> like
> 0: (HUNCHENTOOT:PROCESS-REQUEST #<HUNCHENTOOT:REQUEST {B63CF79}>)
> 1: (WEBLOCKS:HANDLE-CLIENT-REQUEST #<WEBLOCKS-DEMO::WEBLOCKS-DEMO
> {AAF9A19}>)
> 1: WEBLOCKS:HANDLE-CLIENT-REQUEST returned
> "{\"widgets\":null,\"before-load\":null,\"on-load\":null}"
> 0: HUNCHENTOOT:PROCESS-REQUEST returned
> #<SB-SYS:FD-STREAM for "a socket" {B1FA989}>
>
> which does not tell me anything more then I already know.
You've asked for two things: (1) what the browser asks for
(2) what the answer contains.
The above answers (2).
As for (1): in Hunchentoot 1.0 it doesn't work as neatly
as in 0.15 because PROCESS-REQUEST just gets a request
object. Use this instead:
(defmethod weblocks:handle-client-request :before (app)
(format t "uri: ~S~%" (hunchentoot:request-uri*)))
Leslie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---
