[Seaside-dev] WAFile code now in synch with documentation

[Philippe Marschall]

Hi

The target audience of this mail is Seaside server adapter implementors.

As part of fixing issue 480 [1] I stumbled over some inconsistencies
in WAFile. The documentation of stated that #contents should be a
ByteArray but it actually was a String, at least on Pharo. I made the
following changes:
- #contents still answers a String to not break applications but as
been deprecated
- #rawContents answers a ByteArray
- #contentsDecoded and #contentsDecodedUsing: answer a String
- documentation has been updated to reflect the above changes
The new protocol is now similar to the #body protocol in WARequest.

 [1] http://code.google.com/p/seaside/issues/detail?id=480

Cheers
Philippe