>*I think this is a question of fully utilizing SMF security features, >along with potentially maintaining patches to some of the open source >code to bypass their own cross-platform security implementation, and >needing to help users understand why our delivery of a familiar server >is supposed to operate differently than they are accustomed.
I think there's something that requires clarification here. Nothing that I originally proposed requires changing the source code, maintaining a fork, or contributing patches to the Danga memcache code. It was only a proposed change to the manifest file and method script. And from what I can tell, those 2 files aren't even shipped and distrbuted by Danga. For example, I could download the current memcache distribution, replace those two files myself and it would still work perfectly. >This same question* could apply to just about any of the Web Stack >features. It should be obvious why SMF is used (friendlier than generic >SysV init, supports some level of customization of the service without >the user having to edit files, etc.) Okay, it's obvious why SMF is used. What isn't obvious is why an established convention that other third party applications work fine with is considered taboo for Memcache. -- This message posted from opensolaris.org
