I read that the ML xcc library handles "connection pooling" .. .but does it handle "connection caching" ? What I mean is this. Suppose I were to do 10 XCC operations (say run newAdhocQuery). Is there a significant advantage to reusing a session ? Vs. creating a new session for each one.
The context of the question ... I'm working on the ML connector to xmlsh (www.xmlsh.org) and I'm wondering if there is a significant advantage to complicating the API. Right now every ML operation creates a new session (from a connection string like "xcc://user:p...@host:port/DB") then runs the operation. Would there be a significant advantage to instead having a kind of "login" method and then reusing the session instead of creating a new one. Any opinions welcome ! -David Lee ---------------------------------------- David A. Lee Senior Principal Software Engineer Epocrates, Inc. [email protected] 812-482-5224 _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
