Showing posts with label state. Show all posts
Showing posts with label state. Show all posts

Saturday, March 31, 2012

submitting the form to the browser

I am very new to ASP.NET. We have an asp.NET project that is used to show the state of various sql tables/data. The "proposed enhancement" to that is when the data is updated locally (through another application running on the same network where the database is located), the browser (if someone happen to view the same data over the Internet through a browser) should refresh automatically so that the data is ~accurate~ when viewed. I know that browser uses pull technology, and in order to receive a new data, the browser must "request" it (through a control-generated event or a refresh event generated through timer). When the form is posted back to the server and resubmitted, it will "refresh" the browser view. Since the data must appear on the browser within 10-20 seconds of the actual data update, the refresh must be done quite frequently, and the page will constantly reload, so because of that I am not eager to generate refresh events on timer. Is there any way I can push the newly updated page to the browser from the server without any interaction/request from the browser? Is anybody aware of any other technology that I can use it to accomplish this task? ANy help/hint/suggestions are greatly appreciated.

Thank you
olaHi ola,

Unfortunately, there is no other technology that will help you with this issue. You are correct in that the brower uses "pull" technology and therefore there is nothing you can do on the server side to initiate this refresh. The only solution is to use client-side script to refresh the borwser.

Chad
Hi ola,

unfortunately a browser only supports the pull way. But maybe this article can be of help to you:Using IE's Web Service Behavior To Create Rich ASP.NET Applications. I know the next version of ASP.NET uses something like client call back functionality that's able to only update small portions of a page without refreshing the whole page.

Of course using this technique still requires to call a method on a time interval.

Grz, Kris.
Chad,

thank you very much for your reply.
I have additional question. When you refer to a client-side script that can be used to refresh a browser, are you talking about a separate program running on the same machine where the browser is open, or it is something incorporated into the web form code that does it on a timely bases? If it was a separate program (which could know which instance of the browser I need to refresh, which form on that instance of the browser is open and how to envoke the refresh on the browser), it would probably work for me. I will just need to find out how to do it (if at all it is possible). Do you know anything about it? Any ideas/suggestions?

Thank you

ola
ola,

I was actually talking about using a JavaScript timer or using the Meta tags to refresh the browser. I think it would be nearly impossible to write a Windows app to know which browser to refresh when. This would be way more work than it's worth. I think your only solution here is to just put code in your page to refresh the entire page every so often. Sorry I don't have the perfect solution for your problem.

Chad

Monday, March 26, 2012

suggestion to improve cookieless session state

Whidbey finally gives us cookieless forms authentication, which is a great new feature. But, to make it even better the .Net team gave us more than a simple true/false setting. Instead, we can set the "cookieless" attribute of the <forms> element to "UseUri", "UseCookies", "AutoDetect", or "UseDeviceProfile". This level of control and flexibility is amazing, but it got me thinking... why not add this same feature to the <sessionState> element? Currently, the "cookieless" attribute of the <sessionState> element only accepts a true/false value. Would it be possible to extend it to support the same set of values that the <forms> element now accepts? Of course, it would still have to accept true/false as well for backward compatability.I think it's a great idea.

Thursday, March 22, 2012

Support for SVG? ASP.Net, IE & others

There are many unanswered questions about SVG in those forums (see1,2,3,4 among others). What is the state of SVG support in ASP.NET? Is-it already possible to develop a ASP.NET website using SVG? if not what is the support roadmap?

Thanks in advance,
Joannes
http://www.peoplewords.com

Since scalable vector graphics are not a .NET technology but an HTML technology, ASP.NET doesn't care about them. On the good side, it also means ASP.NET fully supports using them, since ASP.NET isn't involved in any way. And since it doesn't involve ASP.NET it's reasonable to expect no answer in an ASP.NET forum.

For SVG you need a compatible viewer. And that's really about it. Google will find you plenty of tutorials, most several years old and still valid.

Jeff