- SmartSockets Java options are simply Java property database files containing keys that begin with ss. Option names and values are case sensitive.
- Many different options are recognized by the SmartSockets Java Class Library for controlling an RTclient’s behavior, and you can add and destroy your own options with Tut.createOption and Tut.removeOption as well.
- Option (property) databases can be loaded from a file, a URL, or a currently open InputStream.
- When an option file is loaded, all values are loaded, overwriting any previous values in memory (except values marked "read-only").
- The Tut and TipcOption classes are used to manipulate SmartSockets Java options. TipcOption objects are not created by your code; they are created and returned to you as necessary by Tut methods.
- Simple option values can be set with the Tut.setOption convenience method and retrieved with the set of convenience methods in Tut, such as
getOptionBool, getOptionInt, and so on.
- More complicated handling of options, such as setting the required or read-only flag or working with enumerated options, requires use of the TipcOption class.
- Enumerated options can have a set of legal values only or legal values and mapped integers, but the two types cannot be mixed within a single option.
- Legal values for enumerated options must be set before retrieving the option’s value, or else an exception will be thrown.
- Values that contain comma-separated strings can be returned as a vector of strings with the TipcOption.getValueList method.
- Custom options can be made read-only with the TipcOption.setReadOnly method.
- The ss.max_read_queue_length limits the number of individual messages in the message queue and the ss.max_read_queue_size limits the total number of bytes in the message queue. The ss.min_read_queue_percentage indicates to what point the message queue threshold must fall before messages will begin to be read into the message queue again.