>>its focus is not to do everything that is done online.<

Yes, I realize that, I'm only making this suggestion to try to minimize your bandwidth. Right now I'm only getting Messages for here in the .NET forum, but when I change my settings and get messages for all forums that I subscribe to, the bandwidth will increase dramatically (VFP gets lots of messages a day!) and I have a feeling you won't appreciate that too much. <g> Same will be true if other people start hitting the WS a lot.


>>Great!! So you'll make the change?
>
>Maybe, as written on the top of the page:
>
>"Some of its functionalities are intended to allow members to download specific pieces of data. It is in no way a replacement for the online interface. Despite the fact that it might be interpreted in some ways as a mechanism to read messages offline, it is not replacing the online interface. Those functionalites only provide some mechanisms to download specific pieces of data which could be used as a local search and for your own archive."
>
>its focus is not to do everything that is done online. So, we added IsNewMessage() and could potentially add this behavior in GetMessage(). But, as we answer those, basically, everyone would want that we support mostly everything that is online and that will never end. The support of two engines is too much. This is why we dropped the offline reader a few years ago. If we start to do the same with the WS, this will simply drop the support of the online interface and it won't proceed as fast as it is. But, we'll probably do this small adjustment. After all, it'll be pretty much locked for that part of the WS.