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. Am i missing
some obvious way to debug things, appreciate the help :)
Regards
On Jul 21, 4:10 pm, "Leslie P. Polzer" <[email protected]> wrote:
> On Jul 20, 12:04 pm, Mackram <[email protected]> wrote:
>
> > So I wanted to check the json part/request handlers. For some reason I
> > am geting null response for the json response
>
> Maybe it's the bug that was reported and fixed here:
>
> http://groups.google.com/group/weblocks/browse_thread/thread/82bef10d...
>
> > and I want to figure out what is being sent from the client and what the
> > server is
> > attempting to respond
>
> Trace hunchentoot::process-request to see the requested URI
> and weblocks:handle-client-request to see what Weblocks returns.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
