Share

C/C++ BEEP Core

Tracker: Bugs

5 cyrus-sasl profile conflict between beepcore c and java - ID: 1233898
Last Update: Tracker Item Submitted ( cissie_carrie )

There is some conflict in the beepcore c and java code
concerning the cyrus sasl profiles.

When the c client wants to initialize a channel with
the piggyback function, it will start the channel with
a blob like this <blob />. Since in c code, the
continue status will be considered as a null status
when making the blob.
The code is like this
switch (scode) {
case STATUS_CONTINUE:
default:
status = NULL;
break;

case STATUS_ABORT:
status = "abort";
break;

case STATUS_COMPLETE:
status = "complete";
break;
}

While in the java beepcore code, "new Blob" function
does not allow a blob which has neither status
attribute nor data between blob tags. It will generate
exception of "No valid data in blob"

This is the java code
if (status == STATUS_NONE && blobData == null) {
throw new SASLException("No valid data in
blob");
}


I do not know which one is correct. Could someone
expert give some advice for this


Ying Huang ( cissie_carrie ) - 2005-07-07 01:26

5

Open

None

Nobody/Anonymous

None

None

Public


Comments

No follow-up comments have been posted.

Attached File

No Files Currently Attached

Change

No changes have been made to this artifact.