Thank you for reply. Hovewer I have two additional questions.

1) Did the issue described in 
http://www.mail-archive.com/[email protected]/msg02014.html
is fixed in current weblocks releases? I just use own-made
installation script which places systems sources in /usr/share/common-
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.

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?

On 9 фев, 18:44, "Leslie P. Polzer" <[email protected]> wrote:
> Hi Ababo,
>
> the demo underwent some redesign a few months ago and the
> screenshots show the previous style.

-- 
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.

Reply via email to