>>>>>>>>
>>>>>>>>When redesigning our main Windows app to a Web app, I timed all of the main features (how long to bring up report x, how long to run report x, how long to go into edit mode on screen y) and ensured that all features were faster. Our app was also designed to look almost exactly like the original, so no re-training was needed. Some users didn't even notice it was web-based, othered than it looked a little different.
>>>>>>>
>>>>>>>Is it really "browser-based", running IN a LAN then?
>>>>>>
>>>>>>Yes. Browser based. Server is outside on the internet.
>>>>>
>>>>>So do they have to put up with "regular internet speed" or do you have some special 'pipe' to assure fast throughput?
>>>>
>>>>Good questions, Jim. Because I have never seen a web app performing as well as windows, let alone faster. But I am sure it is something we don't know.
>>>
>>>
>>>There isn't any deep dark mystery about it. Data does a lot more traveling around on the internet, where a packet can be transferred multiple times on the way to its destination. This is the price we pay for literally global reach and OS independence.
>>>
>>>In my experience INTRAnet apps perform at least as well as desktop network apps.
>>
>>Sorry Mike, but what's the logic here between your two statements "This is the price we pay for literally global reach and OS independence" and "INTRAnet apps perform at least as well as desktop network apps"? They don't seem to follow.
>
>
>They weren't meant to follow. The first statement referred to INTERnet apps.

OK, thanks. I have the incorrect definition of "INTRAnet". I define it as using the INTERnet to run an application, dial-up or otherwise. What is "INTRAnet"?