[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ossig] Quasar Accounting Software for Linux
- To: ossig@xxxxxxxxxxx
- Subject: Re: [ossig] Quasar Accounting Software for Linux
- From: Vincent Lee <leehongfay@xxxxxxxxx>
- Date: Tue, 22 Feb 2005 04:46:35 +0000 (GMT)
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=ZbHS+HuOkeXYdXYJdau2rj/vboP9YIWBRSzACACRVXuMIEyyCIQJMD/PrX2pGJ5f6DHTwYnCcCKW1Mb8ymumKtNV2drTCB+lXdiXtkSqC0il+jO3VUFS6zj4etyGETfxLrSwwgzM7xJZewtq6sW3MeA4K5Jbg9pMNONDQ8MaTXQ= ;
- In-Reply-To: <421AB8F1.6060101@time.net.my>
- Reply-To: ossig@xxxxxxxxxxx
- Sender: owner-ossig@xxxxxxxxxxx
for older web-applications in the 90s, yes, but for newer ones, not really,
because JAVASCRIPT can be CACHED.. just like images embeded in the html pages,
they are not loaded in every other page.. only once.
--- Raja Iskandar Shah <ris.riscniaga@time.net.my> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> imho, for fat client applications, only requests/data need to be
> transmitted over the network. with a web/thin client application,
> requests/data/presentation need to be transmitted. for accounting
> applications, where there is often a master/child grid and plenty of
> input textbox and validation rules, it is more efficient to have the
> forms through thick client. for reports, though, it is mostly server
> side processing (via stored procedures or user defined functions).
>
>
>
> Vincent Lee wrote:
>
> | I suppose, we are looking at which is the optimum point for the
> | following model:
> |
> | Database <--- A ----> processing <--- B ---> presentation
> |
> | For thick client application, processing is done at the client
> | side, so there are a lot of data to be transmitted at point A.
> |
> | For thin client application, processing is done at the server side,
> | only processed data is sent to the presentation layer.
> |
> | The only way to minimize transmission at A using thick client
> | application is to have a lot of "stored procedures" in database,
> | otherwise the overhead of transmitting the data to be processed at
> | client side (A) could be expensive.
> |
> | For thin client application, J2EE solves the problem with Session
> | Bean. If we have to design the patterns ourselves ("easier said
> | than done")... but we don't have to re-invent the wheel, the
> | solutions are out-there, just need to look hard enough :-)...
> |
> |
> |
> |
> | --- Ditesh <ditesh@ameba6.com> wrote:
> |
> |
> |> Vincent Lee wrote:
> |>
> |>
> |>
> |>> surprisingly, web-based front end is actually faster.. for
> |>> example, if I
> |>>
> |>>
> |> were
> |>
> |>
> |>> to enter a field to look for a customer, there are 10 thousand
> |>> records, most thick client app actually search for all records
> |>> on each "key stroke", and
> |>>
> |>>
> |> if
> |>
> |>
> |>> the user were to use 6 characters to locate the record,
> |>>
> |>>
> |>>
> |>>
> |> Not necessarily true. My latest web app searches on key stroke
> |> events so you could have the same problem if problem the problem
> |> was not foreseen. However, if you page your recordset and
> |> display, then you'd always be retrieving only N records at any
> |> point. Throw in some intelligence in your javascript, some
> |> caching on the server end (admittedly easier said than done),
> |> compression/decompression and you've eliminated a chunk of the
> |> problem.
> |>
> |> I think it boils down to having good use-cases and aggresively
> |> testing the app.
> |>
> |> Ditesh
> |>
> |>
> |> --------------------------------------------------------- To
> |> unsubscribe: send mail to ossig-request@mncc.com.my with
> |> "unsubscribe ossig" in the body of the message
> |>
> |>
> |>
> |>
> |
> | =====
> | -----------------------------------------------------------------
> | Wavelet Technology - Your Open Source Software Solutions Provider
> | -----------------------------------------------------------------
> | Unit C-902 Penthouse, Kelana Square 17, Jalan SS7/26, Kelana Jaya
> | Petaling Jaya, Selangor 47301 Malaysia. Tel: 012-6018838
> | -----------------------------------------------------------------
> |
> | CONFIDENTIAL NOTE: The information contained in this email is
> | intended only for the use of the individual or entity named above
> | and may contain information that is privileged, confidential and
> | exempt from disclosure under applicable law. If the reader of this
> | message is not the intended recipient, you are hereby notified that
> | any dissemination, distribution or copying of this communication is
> | strictly prohibited. If you have received this message in error,
> | please immediately notify the sender and delete the mail. Thank
> | you.
> |
> |
> | --------------------------------------------------------- To
> | unsubscribe: send mail to ossig-request@mncc.com.my with
> | "unsubscribe ossig" in the body of the message
> |
> |
> |
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFCGrjxVFIa3VI1W8URArO1AJ9WIkYx+UvXTmdSp4FRUGJAIto4xgCeON26
> NwXdO/9mhIdF7LA1LbzRBD8=
> =hluK
> -----END PGP SIGNATURE-----
>
> > begin:vcard
> fn:Raja Iskandar Shah
> n:Shah;Raja Iskandar
> org:RISC Niaga Enterprise
> adr:Seksyen 6, Wangsa Maju,;;Suite 15-1, Jalan 3 / 27 D,;Kuala
> Lumpur;WPKL;53300;Malaysia
> email;internet:ris.riscniaga@time.net.my
> title:General Manager
> tel;work:+60-3-41496966
> tel;fax:+60-3-41497166
> tel;cell:+60-17-3325065
> url:http://riscniaga.netfirms.com
> version:2.1
> end:vcard
>
>
=====
-----------------------------------------------------------------
Wavelet Technology - Your Open Source Software Solutions Provider
-----------------------------------------------------------------
Unit C-902 Penthouse, Kelana Square
17, Jalan SS7/26, Kelana Jaya
Petaling Jaya, Selangor 47301
Malaysia.
Tel: 012-6018838
-----------------------------------------------------------------
CONFIDENTIAL NOTE:
The information contained in this email is intended only for the use of the individual or entity named above and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete the mail.
Thank you.
---------------------------------------------------------
To unsubscribe: send mail to ossig-request@mncc.com.my
with "unsubscribe ossig" in the body of the message