thank you for reply. I have already solved this problem using individual dispatcher for data receiving acceptor.
On Feb 14, 11:32 am, "Leslie P. Polzer" <[email protected]> wrote: > On Feb 11, 7:57 pm, Ababo <[email protected]> wrote: > > > 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. > > Can you give a small runnable example that demonstrates what > you are experiencing? -- 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.
