Re: Basic application design
- From: "Mike TI" <tanveer@xxxxxxxxxxxxxx>
- Date: Mon, 7 Apr 2008 21:52:04 +0500
April 7, 2008
Things are now begining to make sense. This would be a big project for me
and I would be putting lot of time and resources into it.
I would like to seek your expert advise again: (sorry for repeating)
- The proposed solution would comprise of approximately 6-8 integrated
modules. (Accounting and Operations). Logically the programs will be fairly
complex.
- The solution would be used by approximately 200 company employees.
Additionally approximately 50 customers may be logged on through Web Browser
for inquiry and very limited data entry.
- The company employees would be spread over 4-5 countries.
Q1. Should I go for an ASP Net based solution in totality.
Q2. Should I go for a combination, Client Based application for the 200
company employees and a Web Page application for the 50 customers. (as per
your suggestion I would use ASP.Net Web Services)
Q3. Which would be faster in performance, and, would there be a significant
difference.
Thank you.
Mike TI
"Steve Gerrard" <mynamehere@xxxxxxxxxxx> wrote in message
news:1-mdnTZs-cLlYm_anZ2dnUVZ_qelnZ2d@xxxxxxxxxxxxxx
Mike TI wrote:
Just to make sure that I understand your comments precisely, can you
please explain a little more what exactly you mean by
"2. Web Service running on ASP.Net. All connections to the database go
through this service for data."
You will need to look up Web Service in ASP.Net, I can't explain the whole
thing. :)
Basically, as Spam Catcher said, you setup an interface to the database.
Web methods might include things like GetOperationsData(Parm1, Parm2, ...)
As DataSet, and SaveOperationsData(DataToSave As DataSet) As Boolean.
Using DataSets ties you into .Net, but if that is the plan, it works well.
The web service will then manage the actual database connections and
pooling, and ASP.Net and IIS will manage an application cache and multiple
instances of the web service, as the demand warrants. All done for you,
with endless configuration options.
You then build both a web page app for use in a browser, and a client app
for the serious users, and both apps use the web service to get data and
save data. That lets you put all your serious business and database logic
in the web service. How much functionality you provide in each of the two
applications is then up to you.
.
- Follow-Ups:
- Re: Basic application design
- From: Steve Gerrard
- Re: Basic application design
- References:
- Re: Basic application design
- From: Mike TI
- Re: Basic application design
- From: Steve Gerrard
- Re: Basic application design
- From: Mike TI
- Re: Basic application design
- From: Steve Gerrard
- Re: Basic application design
- Prev by Date: Re: Heavy Application with Multiple Modules
- Next by Date: Re: Why can't ms make API's somewhat compatable
- Previous by thread: Re: Basic application design
- Next by thread: Re: Basic application design
- Index(es):
Relevant Pages
|