Re: Questions...

[JamesTraynor]

well,
I think the problem seems to be what should be in the message and what
the connector should do or be configured to do . Take this simple
message and rough example of what follows
class=message.display
{
Line1=Hello
Line2=The
Line3=Matrix
Line4=Has
Line5=You
Priority=5
}
A slimp3 knows it can only display 2 lines of text, so it knows it has
to display 1 and 2, wait, then 3 and 4 and so on. It also should know
what priority level it shoud display for i.e >2
A Tivo knows it can display 5 lines. It knows it should display at a
certain point on the screen. It knows that the priority changes the
colour based on some set table.
An sms connector knows you are out of the house. It knows it will only
send priority 5+ messages.
A mysql databae connector logs the message as usual, but knows
priority 5+ messages should be displayed in big red text on your
intranet so marks the message accordingly. The CMS now picks this up
etc..
As far as I can see a message is a message, it is either a whisper or
a shout, but nothing more. It should be up to the device to know
how/where/if to display it. After all xAP is a distributed
intelligence protocol so surely this is how it should be.

If I make an app that has to display messages I couldn't possibly make
it have tivo/slimp3/rio/palm remote/new unknown device extensions to
make it work for everyone and for every device. I really think
simplicity is the key for most things.

James