Are subject and project name spaces case sensitive?
Article ID: KB0086071
Updated On:
| Products | Versions |
|---|---|
| TIBCO SmartSockets | - |
| Not Applicable | - |
Description
Resolution:
No, they are not. In the SmartSockets User's Guide, up through version 6.5.0, under the section of "Case" in the Preface, we talk about identifiers not being case sensitive. Subject names are considered to be identifiers seperated by /'s. So although it may not say so directly, this is documented in an indirect manner.
If you really want case sensitivity and you do not have too many subjects you could implement it with a work around. You would register a subject callback for the subject "FOO" (in whatever case you want. Remeber that this call back will handle messages for all cases ("/FOO", "/foo", "/Foo", etc.). In the callback you would get the destination property of the message (which will be in the case that the publisher sent it to) and then use conditional statements to processes different cases in different ways.
Fooey
No, they are not. In the SmartSockets User's Guide, up through version 6.5.0, under the section of "Case" in the Preface, we talk about identifiers not being case sensitive. Subject names are considered to be identifiers seperated by /'s. So although it may not say so directly, this is documented in an indirect manner.
If you really want case sensitivity and you do not have too many subjects you could implement it with a work around. You would register a subject callback for the subject "FOO" (in whatever case you want. Remeber that this call back will handle messages for all cases ("/FOO", "/foo", "/Foo", etc.). In the callback you would get the destination property of the message (which will be in the case that the publisher sent it to) and then use conditional statements to processes different cases in different ways.
Fooey
Issue/Introduction
Are subject and project name spaces case sensitive?
Feedback
Yes
No
Powered by
