Re: MSAccess to Web App
- From: Rick Brandt <rickbrandt2@xxxxxxxxxxx>
- Date: Wed, 22 Apr 2009 23:26:02 GMT
On Wed, 22 Apr 2009 13:24:44 +0000, lyle fairfield wrote:
BTW, 78 records from a server 4200 km away are displayed in one-tenth of
a second. I add this to point out that in my opinion, we pay an enormous
price to run our "web-applications" on remote servers. ASP, ASP.Net, JSP
etc will be much slower, and almost by defintion remote.
Actually I don't know what we mean by a "web" application. I don't think
there are any applications running on a web. Applications run on a
computer, within an OS. We often call a local computer the client, and a
remote computer, the server, but they are both computers. When we talk
about "web" applications I think we are talking about applications that
send information back and forth between clients and servers. This
renders them inefficient and slowwwwwwwwwwwwwwww! ASP.Net is an enormous
joke (Yes, I'm sending an invoice today for an ASP.Net application; it's
what the client wanted but it's still a joke!).
What we need are client-side applications that can use data from the net
and that are small enough to be downloaded quickly. ADPs and HTAs are
examples of these applications. IMO ADPs blow ASP.Net away and that is
why they have been deep-sixed by the anything for a fast buck
corporation.
So, it sounds like you want two-tier instead of three-tier. I cannot
speak authoritatively whether such a set-up is secure or not, only that
as a practical matter there is a huge percentage of the IT world that
holds the view that it is not.
You would need a server port open to the net, a non-starter for many. It
certainly would be at my company. You would need to convince clients
that all of the warnings that IE displays when they open an HTA "can be
ignored". Don't know how well that would fly. Then there's the
firewalls and other anti-malware that you are swimming upstream against.
I'm not suggesting these would affect ADPs, but it seems like they would
be there for HTAs.
I know VPNs solve much (of not all) of these, but in my situation I would
never even think of having every remote user having to go through a VPN.
I have enough trouble getting these guys to copy files correctly.
I personally see little if any performance penalty for having a middle
layer and doing everything via HTTP, but I can't think of any way to
provide an apples-to-apples comparison to your 78 records download time.
I just know that apps that we have re-written from Access to Web-based
are not any slower to use after the conversion.
I use the same performance criteria for web apps as I do in Access apps.
Any form or report should open in under 3 or 4 seconds. Any that take
longer than that and I investigate and tweak to optimize it. Sometimes I
get under the 4 second threshold with those tweaks, sometimes not.
Almost without exception the longer running processes are when the users
have asked for something that had it been up to me, would not have been
implemented. Example; I might set up a search to retrieve 25 records at
a time with paging and they insist that they just want all the results at
once so they can scroll.
Statelessness, thus far, has not been an issue.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
.
- Follow-Ups:
- Re: MSAccess to Web App
- From: lyle fairfield
- Re: MSAccess to Web App
- References:
- MSAccess to Web App
- From: RonG
- Re: MSAccess to Web App
- From: Rick Brandt
- Re: MSAccess to Web App
- From: lyle fairfield
- Re: MSAccess to Web App
- From: lyle fairfield
- MSAccess to Web App
- Prev by Date: Re: MSAccess to Web App
- Next by Date: NewUser: get field from table based on two other fields
- Previous by thread: Re: MSAccess to Web App
- Next by thread: Re: MSAccess to Web App
- Index(es):
Relevant Pages
|
