View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002008IGSTKpublic2005-06-30 08:112005-06-30 08:13
ReporterBrian Blake 
Assigned ToLuis Ibanez 
PrioritylowSeverityminorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOSOS Version
Summary0002008: REQ 05.06.03
DescriptionCommunication component needs to be able to support "Canonical" and "Non-Canonical" communication. "Canonical" communication means that replies are terminated by special characters (e.g. a carriage return) while Non-Canonical communication means that the data record size must be known ahead of time.
TagsNo tags attached.
Attached Files

 Relationships

  Notes
There are no notes attached to this issue.

 Issue History
Date Modified Username Field Change


Copyright © 2000 - 2018 MantisBT Team