Re: Context parameters within Message Bodies

[Stuart Booth]

I was wondering about this topic again this evening, with respect to
email notifications. Currently we have:

xap-header
{
v=12
hop=1
uid=FF125000
class=Mail.Incoming.New
source=KCSoft.POP3.server
}
Message
{
timestamp=Fri, 12 Dec 2003 20:47:24 +0000
msg=11
from="Stuart Poulton" <swp@astro...>
subject=Re: [ukha_d] Ethernet drive enclosure
to=lists@xapfram...
total=11
}

I think the suggestion was to identify the mail server as a hardware
subaddress, and perhaps the username as a subaddress off this. Deep...

So ... (I've marked the new stuff in < > brackets)

xap-header
{
v=12
hop=1
uid=FF125000
class=Mail.Incoming.New
source=KCSoft.POP3.server<:xFx.lists>
}
Message
{
<Server=mail.xapframework.net>
timestamp=Fri, 12 Dec 2003 20:47:24 +0000
msg=11
from="Stuart Poulton" <swp@astro.....>
subject=Re: [ukha_d] Ethernet drive enclosure
to=lists@xapfram....
total=11
}

Here I've added the Server line as it was completely missing before,
as I felt it was implicit in the email address. A bit of mail
forwarding redirection could break that though.

Interestingly I've got the Mail Server and Username duplicated of
sorts, but also aliased as hardware subs, so there's multiple ways to
get at any data you want. How does this feel on a small device level,
Ian?????

One other fairly popular option seems to be to identify some context
data parameter in the message block name:

xap-header
{
v=12
hop=1
uid=FF125000
class=Mail.Incoming.New
source=KCSoft.POP3.server<:xFx>
}
Message<.lists>
{
<Server=mail.xapframework.net>
timestamp=Fri, 12 Dec 2003 20:47:24 +0000
msg=11
from="Stuart Poulton" <<a
href="/group/xAP_developer/post?postID=LbGYcKGRcISc7G8HOwAYrRDNdhcNnq39skjSnYUQnynAjtmjNDYvfyEilsflENE0fmhS1LV_Wg">swp@a...</a>.>
subject=Re: [ukha_d] Ethernet drive enclosure
to=lists@xapfram....
total=11
}

It's compact, it reads well, it looks natural, but I still have a
dislike for moving data items such as this into a block name which
could be describing the content to be found within.

If we wish to avoid duplicate block names in a single message body
then we tend to index them at the moment:

Message.1
{}
Message.2
{}

I daresay "Message.lists" or "Message.kevin" allows a
more textual
index representation.

Thus for any one mail server (the xFx hardware subaddress) i might
have multiple mailboxes being checked and reported on in one status
type message, with each block identifying its context via the username
as an alias on the block name.

S

S
--
Stuart Booth <<a
href="/group/xAP_developer/post?postID=XexrIWnt2cntJGufU4eZtegTAeTNIb5MiV_ACuoIMDmmlP3wWPogxKS63lMZCuKHV0-CP7Px7OC_qBxKl8XI6Q">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net

<a href="http://www.xapautomation.org/";>http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>