First of all, I don't think we need the amendment process on the issue
you raised.
> There are some "legal" workarounds:
> * Use of the Preload action: The intention of this actuin is related to
> content. As a sideeffect, it calls the "preparation behaviour". But,
> preload is only a "hint".
Preload() is exactly included for this purpose. If you look at the
requested actions by Preload(), you can find that applying preparation
behavior is mandatory for the engine as the first action. The "hint"
here is related to the second action, with which you may retrieve
or/and decode the content. Once an object is available by Preparation
behavior, SetData() shall work and be valid on that object. If its
content is not loaded yet, you should do it before applying SetData().
In any case, once an object is available, you can issue SetData(). It
is left for the implementation of the engine, whether contents is
loaded or not. Some engines do it, so that SetData() can be executed
instantly. And some other engines do not it, so that content loading
may be happened if you issue SetData() (or any other actions when the
actual content is needed).
Regards,
** Wataru KAMEYAMA, Dr., ASCII Laboratories Inc., JAPAN
** TEL: +81 3 5351 9711
** FAX: +81 3 5351 9750
** wak@gctech.co.jp ($B55;3!!>D!w%"%9%-!<Am9g8&5f=j(B in KANJI)