Dmitry Beransky wrote:
>
> At 10:56 AM 7/20/00, you wrote:
> >See this link
> >
> >http://www.asptoday.com/articles/20000712.htm
>
> Very interesting (now I want to buy the enitre book and see what else is in
> there). There are some aspects of the new ASP I really like especially
> those targeted at improvements of the workflow (content/code
> separation). It looks to me, though, that this improvement comes at the
> cost of parsing HTML document into a DOM tree (although, I've always wished
> there were a cheap way to manipulate the DOM of a document on the
> server). I've also noticed that the markup used in the excerpt is a weird
> combination of HTML and XHTML (those <P /> tags). I wonder if ASP+ pages
> are [can be?] required to be written in XHTML to speed up the parsing time...
>
Whatever makes it into Apache::ASP, I assure you, I won't
be doing any DOM tree parsing. My approach tends to be
look just for what you need to look for in the HTML
and trigger off that while parsing, so when using XMLSubsMatch
or the <asp: ...> controls, the asp parser would only look
for <asp: ...> For automatic form filling, would just be
picking out <form>...</form>, etc.
These features can then be activated per need, thus a user
has control over what compile time performance their
environment will have.
Further, ASP scripts only get compiled once per process,
and only once per server with smart use of Apache::ASP->Loader()
so even complex compile time parsing won't be as expensive
as one might otherwise think.
As we move forward with integration of ASP+ features into
Apache::ASP, please keep me up on which features you would
find particularly useful to yourself.
-- Joshua
_________________________________________________________________
Joshua Chamas Chamas Enterprises Inc.
NodeWorks >> free web link monitoring Huntington Beach, CA USA
http://www.nodeworks.com 1-714-625-4051
