Has anyone found weird values for the server_time values from the
XRecordIntercept structure with regards to requests,replies or errors
? I'm wondering if this is an RECORD extension bug ? or
something with xnee ? or if it is a valid field for messages other than
events ? Has anyone else encountered this ?
I find that the server_time value for events are ok but for requests it
looks like garbage. For the events the server_time increases
as the recording goes along ( and doesn't decrease ) - so I'm assuming it
is valid, but for the requests it isn't even close to the same value as
the events and jumps all over the place. The same thing
occurs with the various X servers I have tested with ( Exceed, NCD, IBM
etc). I thought I would check the RECORD spec. to see if it
is a valid field for request but I'm still not sure what this means as
far as requests goes:
"The server_time member is set to the time of the server when the
protocol was recorded. It is the time that was attached to this protocol
element in the reply, if so specified by datum_flags, or else the time
from the header of the reply that contained this protocol
element."
I have my datum flags set to:
xd->record_setup->data_flags =
XRecordFromServerTime |
XRecordFromClientTime |
XRecordFromClientSequence;
Thanks - Any help appreciated.
Janice
Waddick
Voice:(416)622-5550 Ext. 209
Sr.
Consultant,
Fax: (416)622-8884
RAD International
Ltd.
http://www.radintl.com
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to which they
are addressed. If you have received this email in error please notify the
system manager. Please note this email and any response to it, may be
shared, for business purposes, with other employees, subcontractors,
agents or representatives of RAD International Ltd. (herein known as
"the company"). Any views or opinions presented in this email
are solely those of the author and do not necessarily represent those of
the company. Finally, the recipient should check this email and any
attachments for the presence of viruses. The company accepts no liability
for any damage caused by any virus transmitted by this email.