Re: Performance question

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: DalePres (don-t-spa-m-me_at_lea-ve-me-a-lone--.com)
Date: 02/10/05 

Date: Wed, 9 Feb 2005 22:42:53 -0600

Lubomir,

Keep in mind that all the menu controls, server generated or client
generated, will depend on the client allowing javascript. The primary
difference between the server controls and client controls is how the
javascript is generated.

For client-side menu controls, the javascript is generally either stored in
a script file that is included by using the src attribute of a Script tag or
by including the javascript directly in the HTML file. Server-side menu
controls, on the other hand, generally (but not always) create the
javascript from code in the application dll.

The main consideration I would use in determining whether to use client or
server side menu controls is whether the contents of the menu must be
created dynamically based on logic in your application. If the menu is
always consistent, use a client side control. If your menu contents must be
modified based on your business logic, then use server-side controls. In
fact, this consideration applies to all the controls on your page.

Keep in mind that neither client-side menu controls or server-side menu
controls are going to work if the client has javascript disabled.

HTH

DalePres
MCAD, MCDBA, MCSE

"Lubomir" <Lubomir@discussions.microsoft.com> wrote in message
news:C5B573B4-6153-40FC-AE26-992927C262D2@microsoft.com...
> Hi,
>
> I would like to know your opinion about .NET menu server controls from
> performance point of view.
>
> It is a good idea if a menu is running on a client machine: a response is
> quick and the server time is not used. However, implementation of a menu
> in a
> java script often results in a messy source code, and there can be
> problems
> if web browser on the client has disabled JavaScripts.
>
> Menu implementation on the server side is clean and runs without problems
> in
> a browser. However, it takes the server processor time and it needs to
> make a
> route to the server and back every time a user hit a menu.
>
> I gave a look at MSDN newsgroup page and it seems that MS used server-side
> menu. It works fine (for me), even I don't know how strong hardware was
> necessary to use for achieving this performance.
>
> What is your experience? Generally speaking, is it a good idea to
> implement
> a menu in a form of a server side control?
>
> Thanks,
>
> Lubomir
>

Relevant Pages

  • Re: Tier3 today - And Flex-it like NASDAQ (*Only better!*)
    ... FlexBuilder, or just working on the FABridge functionality in general, you ... ArrayCollections are completely accessible via the Javascript in ... Broadcasted server to client messages, ...
    (comp.os.vms)
  • Re: Visual Studio only debugs javascript in .js files not .aspx fi
    ... An ASPX page is a class that generates HTML ... from the server. ... including any literal JavaScript in the page code, ... is used by the client browser to execute JavaScript on the client side, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: newbie question
    ... They also render JavaScript, but that is generally for the purpose ... of handling client-side events on the server. ... Controls as well. ... >> compiling without Visual Studio, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: VB.net and ASP.Net Typed Datasets
    ... upgraded the "backend" or data layer to SQL Server 2005. ... For these reasons we wish to use ASP.net, to have a Smart Client. ... inadequacies with the web controls and the winform. ... used in any .NET language. ...
    (microsoft.public.dotnet.framework.adonet)
  • Tier3 today - And Flex-it like NASDAQ (*Only better!*)
    ... Bootcamp) and then click on "Interactive Charts". ... are laid bare and fully accessible by your Javascript. ... Broadcasted server to client messages, ...
    (comp.os.vms)