Re: Message Queuing

[James <james@xxxxxxx>]

.. trying to cope with a 152 message

>flood from my poorly configured,
>show-me-everything-even-if-its-home-shopping xAPTV update of 76
>channels...
>
>(James... Don't take it personally... It's ME that has it poorly
>configured, not you...)
>
>
but it is a fault with the app. News was the same as it would send its
regular broadcasts all together causing big run of messages. News3 fixed
all that with alot of balancing of send/downloads etc. so is alot kinder
on the network. TV needs the same treatment and it will come, don't
worry. It won't stop it all though as with TV you could in theory have
all your 72 channels changing program at the same time and it would be
important to get that info out as soon as possible, especially if you
get a xAP linked videorecorder!
The big thing to remember when dealing with a  xAP receiver is to drop
unwanted messages as soon as possible. I know with a database logging
app that may not be possible but it's worth keeping in mind as there's
no point in processing a message that's of no use. In my (very nearly
released (honest)) touchscreen app as it runs on slower machines this
became a big issue and simply adding a quick check after the class= in
the header solved most of the issues, it also doesn't help that vb isn't
that fast :-( With a log all messages db app you won't get this luxuary
so an input queue is about all you can do unfortunantly. Most , non US
TV, xAP networks stay below 100mpm which is less than 2 messages per
second, mines around 45  at the mo . The highest rate i've heard of was
KevinH testing the netiom-xAP in loop and that hit 3000+  but that quite
an extreme. Stuart's message flood app is naturally a good stress tester
for the toolkit.


James