Gertjan 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
just one point >>c) On long time outs - this is an intranet app - the user does not >>want to be logging on every 10 minutes, typically they open the >>browser in the morning, and keep swopping back to it - do some work, >>answer a telepone query - a la old style terminal app > >But they don't have to (login every 10 minutes) -- unless you use >hyperevents. Not just for hyper events - don't use em 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 it's not what the user wants - having to log on and navigate to the required page on every session timeout due to inactivity - hence I use 8 hours - keeps them up during the working day but will time out overnight if they have been naughty and close-crossed the browser There is also the licensing side, but it's the UI that's the important thing 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 Peter
