Follow me on Twitter at Twitter.com/wbm
FYI, I'm blogging most of my stuff over at More Wally now.
You might want to add my rss feed to your reader at:http://morewally.com/cs/blogs/wallym/rss.aspx
Sys.Profile.set_autoSave method in Atlas - Wallace B. McClure

Wallace B. McClure

All About Wally McClure - The musings of Wallym on Web, HTML5, Mobile, MonoTouch for iPhone, MonoDroid for Android, and Windows Azure.

News

Personal Blog

Work Blog

.NET

Book Authors

Business

Family

Friends

Georgia Tech Bloggers

Personal

Archives

Sys.Profile.set_autoSave method in Atlas

If you are using the ASP.NET 2.0 profiles in Atlas, you want to pay attention to the Sys.Profile.set_autoSave(boolean).  If you pass a true in, changing any value in a Profile results in the updating of the profile on the server.  Setting it to false gives you much more control.  Also, if you are seeing the updates being performed on your server multiple times, you might want to look into this.  I had some example code that had the udpates being made multiple times.  When I set the value to false on a page load, the problem of mutliple calls went away. 

Overall, I think that this is very cool.  I can see why they have this and I think it is a good idea.

Wally

Posted: Apr 11 2006, 09:07 PM by Wallym | with 1 comment(s)
Filed under:

Comments

Plip said:

What's the overhead of making a single request, say in terms of the overall transmission in terms of bytes to transfer up the setting of a propfile propery called "Name" and giving it the value of "Wally" ?

Some metrics would be cool in demonstrating how much is saved here. Obviously its also client side and server side processing.

# April 12, 2006 4:05 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)