It probably does this to keep it simple. If the pooled connection had to keep logging to different accounts for each of its connection it would have to keep track of where it was and which connection used which account. This would likely slow it down and open an attach vector that could be exploited.
Not impossible to do - but may not be a good risk vs. return for Rocket. At least until we can get more vendors to host multi-customer based servers. Colin -----Original Message----- From: Bill Haskett That always seemed just "/*wrong*/" to me! I could never figure out why a connection pool license would work this way. Sure puts a crimp on a number of potentialities. :-) Bill ------------------------------------------------------------------------ ----- Original Message ----- *From:* symeonb > A pooling connection goes into 1 single account yes > > We have a special "shared" account for the pools with voc pointers to the > real customer accounts . Part of the message passed to the backend is the > customer so it opens the correct files etc. > > -----Original Message----- > From: Bill Haskett > > Symeon: > > Your "pooling" connection is set up for a single dbms account, correct? > You'd need a separate "pooling" license for each dbms account to access, > correct? > > That is some dance you need to go through to do what, basically, the > computer is supposed to do! > > Bill _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
