Peter Cooper wrote: >I think we are sort of agreeing - or at least it's horses for courses >and you choose the best thingy to meet the requirements
Agreed. >my app is secure so they have to log on and then all the pages are >(PRIVATE=1, ENCODED=1) plus they have to be logged on Right, that's a good point - I've never used private/encoded pages, so I wasn't aware that they would interfere with automatically re-creating the session. >it's not what the user wants - having to log on and navigate to the >required page on every session timeout due to inactivity Obviously, although navigating to the page they originally requested after re-login can be done automatically. If the only way to avoid the re-login is a long session timeout, then that's what you need to do. This again calls for a looser coupling between sessions and licenses, *especially* on (named) user licenses. I know this is probably not going to happen, but it would be nice if someone from ISC was reading this and could respond from their side -- AFAICS a looser coupling would present no significant licensing issues (at least, none that can't be worked-around already), but I could be mistaken. >And as I said ISC did me a deal on a "spare" license to get them over >the problem of not being able to get past the logon-screen That is nice of them, but unless they volunteer this extra license to everyone developing CSP apps, it is hardly a solution. Gertjan. -- Gertjan Klein
