> Weblocks computes on each client request the path of the application, > which (if i understand correctly, if not set by the developer > explicitly) is calculated from the path of the ASDF-system to which > the application belongs. For that Weblocks calls asdf:system- > definitions-pathname, which on it's turn traverses all known > directories known to ASDF to search and does a PROBE-FILE for .asd > files with the name of the system searched. And that can take a while. > Not knowing if this is an intendet behavior of Weblocks I implemented > a small function, which memoizes the .asdf locations per system, which > I turn on before loading Weblocks. Then - the demo responds allways in > less than a second.
That's interesting. Could you submit a full patch? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
