Actually it doesn't work. I'm trying to achive the following behavior. My server which receives data from smartphones is working on port A on some web-path. All other paths don't give any response (no default pages). The weblocks I have on port B (80) is bound to several web- paths without default page. But in reality I have the following. When I start weblocks with port B I have it also appears on port A overriding the receiving data handler. When I invoke kind of (push 'my- dispatcher hunchentoot:*dispatch-table*) my handler becomes alive but the default weblocks page persists.
On Feb 10, 8:47 pm, Ababo <[email protected]> wrote: > Thanks, I'll try that. > > On Feb 10, 5:05 pm, "Leslie P. Polzer" <[email protected]> wrote: > > > > > On Feb 10, 1:22 pm, Ababo <[email protected]> wrote: > > > > lisp/systems/ as root and this approach is not working with weblocks > > > which is creates files inside its own sources directory (but should > > > place them in some temporary one. > > > It's best to have one Weblocks installation per project. I agree > > it would be nice to have flexible temporary directories, but it's > > not going to happen unless somebody is annoyed enough by it > > to fix it. > > > > 2) I'm writting a server which uses hunchentoot for receiving client > > > data via http/post (client is a software agent on smartphone). When I > > > start working with weblocks it kills my easy handler in hunchentoot. > > > Is there a possibility to bind weblocks responce only to single web- > > > path preserving all other http-handlers without deep diving into > > > weblocks internals? > > > A simple solution is to push your handle in front of Weblocks in the > > dispatch table: > > > (asdf:oos 'asdf:load-op 'weblocks) > > (push 'my-dispatcher hunchentoot:*dispatch-table*) > > > 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.
