Hello,
I agree with this and am very sorry. When I first started doing this about
2 years ago I was just learning and I actually used a different CT-API spec
to write the interface. If anyone has a correct CT-API skeleton that I can
use - I'll put it on the web site so that anything new can be
Hi all
I encountered a severe problem with the current CT-API interface used in
MUSCLE. The skeleton defines the interface to be
int CT_init(unsigned int Ctn, unsigned int pn)
int CT_data(unsigned int ctn, unsigned char *dad, unsigned char *sad,
unsigned int lc, unsigned char *c
