did i read your article before posting my comment on your blog entry ? was it
posted before ? am i confused ?
anyway your article is interesting and shows how to understand the way domino
and your browser work (or not) together. and it really takes time to apprehend
things like this...
we (domino developers) surely need to share our methods to analyse a problem,
as mush as we need to share our code.
Maybe one or two short articles would be interesting, dealing, for example,
with the http posts (why multipart/form-data and not urlencoded ?) and
ethereal, how do you know what domino receives, how it is decoded, or more
generally how to debug some code, which are the most famous domino bugs, what
is the code domino generates about (_doClick and so on)...
we would then have a domino bugs killer cheat sheet...
did i read your article before posting my comment on your blog entry ? was it posted before ? am i confused ?
anyway your article is interesting and shows how to understand the way domino and your browser work (or not) together. and it really takes time to apprehend things like this...
we (domino developers) surely need to share our methods to analyse a problem, as mush as we need to share our code.
Maybe one or two short articles would be interesting, dealing, for example, with the http posts (why multipart/form-data and not urlencoded ?) and ethereal, how do you know what domino receives, how it is decoded, or more generally how to debug some code, which are the most famous domino bugs, what is the code domino generates about (_doClick and so on)...
we would then have a domino bugs killer cheat sheet...