to the web right now, surely documenting AOLserver makes
sense, even from a bean-counter perspective.We *have* actual tech
writers in this company (unless we laid them all off)---has anyone tried
to get some of their time lately?
IRA
--
AOLserver - http://www.aolserver.com/
To Remove yourself
eight=<%=$img2h%> border=0 alt="<%=$str6%>">
<% else %>
height=<%=$img2h%> border=0 alt="<%=$str6%>">
<% endif %>
The readability difference may not be so apparent given the lack of
formatting in this email, but the difference in m
Is there a document anywhere listing the changes between AOLserver 3.x
and 4.x?We're still running 3.4.2 and we'd like to upgrade to 4.x,
but I have no good way of predicting how much of our code we'll need to
modify.
Thanks--
IRA
--
AOLserver - http://www.aolserver.
t I do stand by it. I've spent
the past year working with AOLserver after years of working in other
environments, and quite frankly, it hasn't been very much fun. The
documentation is incomplete, AOLserver has numerous idiosyncracies,
there are quite a few features I miss from othe
ious
> config
> junk, wasn't to complicated. Basically it required calling a
> function to
> collapse all the blocks together at the end of parsing -- the key
> function is
> below.
Wow, thanks! You mentioned that there might be a performance hit with
this option
> Wow, thanks! You mentioned that there might be a performance hit with
> this option--any guess as to how significant that would be?
>
> IRA
>
>
>
>
> Sorry -- no data. I'm guessing that for all but the busiest and/or
> memory
> consuming th
like debuggers is
probably a good start. Telling developers they have to do things
*your* way is a quick way of getting them to look elsewhere for their
solutions. :-)
IRA
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROT
