Peter Cooper wrote: >Gertjan > >>Wouldn't the factory and the ODBC connections require a license as >>well? If so, this still doesn't help. > >yes but it's from the server so would be having the 12 count per >license slot
CSP sessions can have those as well, as I showed. The connection count, in itself, has nothing to do with where the connections come from. The problem is that the CSP engine tries to handle the licensing, before allowing the programmer to resolve whether a connection belongs to an existing license or should create a new one. >and the connection would be dropped straight away and these >connections have no grace period True. But in the situation you described (an eight-user license, and eigth users all online at the same time), there would be no license left for the ODBC connection required to do the login, if one of the users starts a new browser session -- which is the situation we were trying to support. This still requires trick with the licensing, I'm afraid. > $system.License.DeferUserIdentification(1) > >this seems to be what we want - but does it work and if so how?? The documentation on this is sadly lacking, so I'm not sure what it is supposed to do exactly. My tests indicate, though, that it does not work the way I'd expect (read: like to) for CSP sessions. Gertjan. -- Gertjan Klein
