I am trying to stick to the plan outlined a couple weeks ago on the 0.8
release. The goal being to get the mostly stable current development
version in CVS released as 0.8 in the near future.
There are a couple of recent issues that I wanted to touch on.
** Regarding the Page.writeDocType() method **
The 0.7 behavior was to return a 4.01 transitional doctype. The
current behavior is to return nothing. However this apparently breaks
some 0.7 installations, and debugging such a problem can be a pain. If
left as is, it needs a good comment in the release notes.
Chuck, I think you were the one that changed the default because of
instability in Mozilla. But it is not clear to me anyway that the
Mozilla problem remains. Any thoughts on this?
My interpretation of the consensus on the mailing list is that we
should restore the 0.7 behavior, and add a note to the Release Notes
highlighting the potential problem of an incorrect DocType string for
the HTML you are generating. Also noting that the behavior has reverted
to 0.7 as opposed to following the last several months of CVS behavior.
If anyone wants to suggest some other DocType strings and information
to be added to the Release Notes, Users Guide, or to the writeDocType
doc string please do so.
I don't have a high degree of confidence in this approach not being a
pain, because the CVS trunk has behaved differently for so long. But
it seemed like the way to go from the e-mail threads.
** Regarding the SessionMemoryStore and saving to disk. **
It appears unlikely from the e-mail thread that many people are using
the SessionMemoryStore relying on the save to disk behavior. The
direction I think we are leaning is to remove that capability of the
SessionMemoryStore, making it memory-only and not persistent.
While the risks of changing this for 0.8 may be low, I am not sure that
the benefit in changing the paradigm from established behavior is worth
it at this point. I currently lean towards leaving this until after 0.8.
** Disclaimer **
I am trying to err on the side of caution, and expeditious release of
0.8. Beyond that, we can come out with a 0.8.1 if necessary if we
decide we want more changes in the way things work.
-Stuart-
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel
- Re: [Webware-devel] 0.8 b2 issues. Stuart Donaldson
- Re: [Webware-devel] 0.8 b2 issues. Ian Bicking
- Re: [Webware-devel] 0.8 b2 issues. Stuart Donaldson
- Re: [Webware-devel] 0.8 b2 issues. Aaron Held
- Re: [Webware-devel] 0.8 b2 issues. Stuart Donaldson
- Re: [Webware-devel] 0.8 b2 issues. Aaron Held
- RE: [Webware-devel] 0.8 b2 issues. Geoffrey Talvola
- RE: [Webware-devel] 0.8 b2 issues. Ian Bicking