Extra parameters in Heartbeat messages from xAPFramework

[Stuart Booth]

Hi folks,

James spotted a field appearing in my Heartbeat messages shown on a
message viewer console that wasn't originally being transmitted,
notably the very underused process ID field e.g.:

xap-hbeat
{
v=12
hop=1
uid=FF125000
class=xap-hbeat.alive
source=KCSoft.POP3.server
interval=60
port=3641
pid=1520
}

This turns out to be a xAPFramework buglette that you've found, James!
I found that what's happening is that xFx fills in the PID value
automatically, from that machine, as if you were going to send it.

When it reads in a h/b message it fills in all the values but because
they didn't contain a PID field in them, it leaves the default value
in there regardless.

Gee, that's been in there since the humble beginnings. That's 2 or 3
of those you've found. I probably owe you a whole packet of Mars Bars
now! :lol:

All my xFx apps use the default h/b object which will therefore always
have the PID field filled in, so no wonder I've never noticed before.
I don't tend to pay too much attention to the h/b messages in general.

Thanks for that. Fixed in the next available build.

S
--
Stuart Booth <<a
href="/group/xap_automation/post?postID=YksLU0gQXTYKJe0-3kXA6c_wDHU1gEZ8toSeE9chbaN3qNnfVYSt1Bu8uZc9p7bQ53dvpnMw5Z0IbM_ihHz17BAI">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>