[Dxspider-support] Long comment fields

Kelly Jones kjones at sullivan1.com
Sun Feb 9 07:34:39 GMT 2003


Hi Charlie,

Yes, I am familiar with the DXCC entity being added on the end of the 
comment field.  However, when that is done, the entire length is still 30 
character, including the country.  So the timestamp is still in the 
expected place.  My feeling the DXCC entity is still part of the comment 
field if you think of it 30 characters long.

Having a "sliding" field length is a headache if you have an application 
that is looking for fixed length fields.  I realize we really have no 
standards, but do badly do we break "convention"?  I guess that is the 
$10,000,000 question.

Kelly - KE9KD


At 02:07 AM 02/09/2003 -0500, you wrote:
>Kelly:
>You raise an interesting point.  A week or so ago I was speaking with
>K1EA (CT) about exactly this subject.  The issue, however, is not just
>with DXSpider.  At least one other cluster s/w package "takes liberties"
>with the comment field, in this case putting a DXCC abbreviation just
>prior to and just after the time.
>I looked at the old Packetcluster protocol, but did not see any
>specifics relative to the length of the comment field.  In days of old
>when Packetcluster and CT were being developed, K1EA and AK1A pretty
>much knew the details of the other's s/w.
>Now, there are multiple cluster packages, multiple contest logging
>programs, and multiple general purpose logging programs.  Unfortunately,
>other than the old Packetcluster protocol, there's no standard.  Hence,
>this problem may be with us for a while.
>
>73 charlie, k1xx
>
>_______________________________________________
>Dxspider-support mailing list
>Dxspider-support at dxcluster.org
>http://www.tobit.co.uk/mailman/listinfo/dxspider-support






More information about the Dxspider-support mailing list