It looks like Proton requires SASL configuration to come from a named file. This is bad, because it assumes a) there is a file system and b) the proton app deployer can modify it.
I was thinking about adding pn_sasl_config_string(pn_sasl_t*, const char*) So the application can get the config from wherever it pleases or construct it programatically without assuming a filesystem. Does that make sense? What about the SASL database? Or am I barking up the wrong tree and SASL is just not intended to be usable in non-filesystem environments? Cheers, Alan. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
