[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.remoting

Re: Button click with Remoting

Sahil Malik

6/7/2004 6:49:00 AM

John,

If every button click is throwing a remoting call, you are probably not
archiecting the application right.

Remoting emphasizes that you must use Chunky, not chatty interfaces, viz.
think of the disconnected model ADO.NET and .NET encourages, download all
that you might ever need as a dataset, or your custom object, and do all the
button pressing, tab switching UI changes etc. on the client, with the final
remoting call going when the user hits "Save".

Therefore, instead of remoting every single call, you now remote only two
calls.

Why is this a good architecture, 6 years back, it took 1/2 a second to ping
tokyo, and it took 1 hour to download 1 MEG from Tokyo.
Today, it takes 1/2 a second to ping tokyo, but 2 seconds to download 1 MEG.

Downloading tonnes extra is not a big deal, it is the repeated network calls
that is a big deal.

Hope that helps :)

- Sahil Malik
Independent Consultant
You can reach me thru my blog at -
http://www.dotnetjunkies.com/weblog/s...



"John" <anonymous@discussions.microsoft.com> wrote in message
news:17aa101c44969$99d84de0$a501280a@phx.gbl...
>
> How should I handle the user clicking a button that calls
> an asynchronous SAO? Should I disable the button until
> my call returns? Just curious about what over people do.
>
> What about forms with lots of buttons and lots of tabs,
> should I disable everything until my call returns?
>
> Thanks in advance,
> John