Just some quick notes on things that don't look to be in nstcl
- No nsvs
- No Registered filters
- No Scheduledprocedures or startup/shutdown
- No internal handling of persistent db connections using shared pool in thread safe manner and not sure if any part of api thread safe being that it is a shell extension
- No comparable nsd config file exists for shell
- No ns_conn structure
- What about modules that are required how would you handle ns_cache, etc.
While I greatly admire nstcl I don't think people should be too optimistic about how *easy* that approach may be and I'm not sure the
end result would be even on a Java level.
