| From: | Sam Jordan |
| Date: | 18 Dec 99 at 15:20:35 |
| Subject: | Re: [warpup] Asynchrone... |
Am 18-Dez-99 schrieb Steffen Haeuser:
>Hi!
>>Hmmm... so far, I have found the asynchronous approach to be ever so
>>slightly *slower*, in the above situation! Go figure :) Looks like
>>you are right.
>Yes, looks like my own experiences with it. And i think Sam once also told
>that it is not worth it, and i sometimes got a similar report of a demo coder
Meanwhile I have to say that it's not only not useful, it simply doesn't
work reliably (when using XMsg). I found a bug inside the current WarpOS
implementation which leads to the message body not beeing correctly
invalidated. I will correct that and will sometimes do a new release
(minor step, maybe 4.1).
Particularly the partial cache flush (using SetCache) doesn't work
correctly. If anyone uses the partial cache flush explicitely, he should
consider use a full cache flush (start and length set to zero), this
works correctly.
bye