Skip to main content

Client CallBack in ASP.NET 2.0

Whidbey, a tool to bring user and developer closer, more easily. Sounds good, does'nt it? Anyway, I heard about the call back functionality they were implementing. Sounded too good. Great feature, etc. etc. Played around with it and it looked really good, useful, etc.etc. Then started the thought process. How are they doing it??? I had heard about another way, using an ActiveX object called XMLHTTP.
Then some guys discussed about whether client callback worked on browsers such as Mozilla, the doubt level increased especially when a bug was reported on Visual Studio bug tracker. So I explored, it was quite simple. When I included code to get a event reference to the callback functionality ASP.NET included a script (.js) file. I got out this file and opened it in good, old TextPad..... Goodness, gracious it looked extrememly familiar. Have a look. So I guess technology is not new but just implementation has been changed, for the better????? Maybe.......... :)

Comments

Post a Comment

Popular posts from this blog

B.O.F.H.

Was browsing the net, and found some old link to BOFH. Not sure as to how many used to read PCQuest some time back when it used to come, but i remember reading them, with of course re-reads and re-re,etc...i can go on you know. Anyway, it's about a system operator who is bugged by no-brainers asking silly computer related queries, and this guy repling with wierd answers. I had never known the origin of this character, until i saw this . Anyway for those who have never read BOFH, here are two of them.
Post a Comment
Read more

So you have your website deployed in PROD ... now what ??

Posting on behalf of Usr.Web.Speed - My previous job had been to architect and develop websites for various customers. During that time my team and I have architected and developed various web applications mainly for enterprises. (But below info is not restricted to enterprises) Other than the usual development and testing tasks involved, our focus area was to abide by multiple SLAs. One of the primary SLAs was to provide the users of our websites a very low (usually subsecond) response time (or page load time). To adhere to this SLA, we did multiple activities, in code, process as well as infrastructure. These include (but not limit to) - Using best practices including (http://developer.yahoo.com/performance/rules.html) Determining the optimum number of calls to the databases, open connections, etc. Providing the fastest mechanisms to download associated content (such as stylesheets, JS files, etc. over CDN) And debugging the reason for the slowness of the websites, when ...
Post a Comment
Read more