RE: Message Queuing

["Sullivan, Glenn" <gsullivan@xxxxxxxxxxxxxx>]

------_=_NextPart_001_01C57B61.5D23647B
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

What do you do in viewer?  Viewer seems to catch everything, and frankly,
I've noticed that I get almost NO dropped messages when viewer isn't
running...

I wonder if that's it... running two programs that attempt to process all
the messages that are inbound...

Regardless, the problem still exists.  Too many messages for everything to
process at once.  I'm going to start queuing inbound messages I think...

Glenn

________________________________

From: xAP_developer@xxxxxxx on behalf of Stuart Booth
Sent: Mon 6/27/2005 3:01 PM
To: xAP_developer@xxxxxxx
Subject: Re: [xAP_developer] Message Queuing



On Mon, 27 Jun 2005 07:55:50 -0400, "Sullivan, Glenn"
<gsullivan@xxxxxxx> wrote:

>I'm just wondering how other people handle situations like this?  I
>figure it would affect any listening application that takes any time at
>all to process the messages it is listening for.  Is there a feature of
>xAPFramework.net that I'm not seeing that handles this?

I'm afraid not. I've never noticed this problem before but this may be
just because of not detecting it rather than it not happening!

I sort of left that bit as an exercise for the future as currently xFx
just fires an event when a message arrives but could easily, and
ideally should, queue things up internally.

I'm in the middle of some mods (temperature permitting) to sort out
once and for all, the message block/header pair juggling that xFx does
(waves at James and Kevin re. this feachur they've had to put up with
and nagged me about for years now... ;-). This will also tidy up the
access to the block and header pairs that you brought up earlier.
Whilst I'm there it might be worth adjusting the area you mention in
this thread.

A transmission throttle sounds like an interesting addition too, but
that presumes all application output goes through a single funnel (in
my own apps I tend to use xAPSender.ApplicationSender exclusively so
this is no problem), or as inbound messages are detected the
transmission backs off Ethernet collision style I think?

S
--
Stuart Booth <stuart@xxxxxxx>
xAPFramework.NET - a xAP software development framework for .NET

http://www.xapautomation.org/ 
     http://www.xapframework.net/