I have put online one more pre-release version of the Ajax.NET Pro [1]version. See the list of changes and bug fixes (not complete):
Posted by Michael Schwarz on Monday, October 31, 2005
I published a new pre-release to the Google Ajax.NET Professional group [1].
Posted by Michael Schwarz on Friday, October 28, 2005
If you want to use a converter for your classes you can add the JavaScriptProvider attribute to your class that it will be used without the need of changing the web.config. This will allow developers to use components from third parties without changing their web.config.
Posted by Michael Schwarz on Saturday, October 22, 2005
Because I got a lot of feedback that sometimes it would be nice to have my own converter I included the converter interface again. The default converter like IEnumerable, IList, NameValueCollection, HtmlControls (!!!!) , DateTime, all DataSet objects and IDictionary are included as source code.
Posted by Michael Schwarz on Friday, October 21, 2005
In the next version I'm using the IHttpAsyncHandler instead of the synchronous handler IHttpHandler. The request now will run in a separate thread that cannot access the HttpContext.Current object. For this reason you have to implement the IContextInitializer interface to get the HttpContext in your class:
Posted by Michael Schwarz on Friday, October 21, 2005
With the new version you are able to get the real JavaScript wrapper objects that are used internal to representate the JavaScript objects. This will allow you to post any object from the client-side JavaScript code you want that does not exist as a CLR type:
Posted by Michael Schwarz on Friday, October 21, 2005
Today I have finished a working demonstration using AJAX as a TCP connection. With that demonstration you can use a HTTP connection as a real TCP/IP connection:
Posted by Michael Schwarz on Friday, October 21, 2005
My parents are currently on a business trip in South Africa, and they saw this AJAX writing:
Posted by Michael Schwarz on Friday, October 21, 2005
"Clients that use persistent connections SHOULD limit the number of simultaneous connections that they maintain to a given server. A single-user client SHOULD NOT maintain more than 2 connections with any server or proxy. A proxy SHOULD use up to 2*N connections to another server or proxy, where N is the number of simultaneously active users. These guidelines are intended to improve HTTP response times and avoid congestion."
Posted by Michael Schwarz on Thursday, October 20, 2005
AJAX Date Picker is a free ASP.NET 2.0 calendar control that utilizes AJAX techniques to get data from the server without an entire page postback. You can specify the clickable dates on a given month as well as other days like holidays, etc. A great application for this control is for those sites that uses some reservation system to select valid dates. For example a travel site can use this control to render only valid dates. This controls limits the user on what dates to click. As a result you have a hybrid client/server validation.
Posted by Michael Schwarz on Friday, October 14, 2005
You can download [1]the changed chat [2] demo application at the Ajax.NET Professional Google group [3]. This is using an internal version of the library that will not have the memory bug.
Posted by Michael Schwarz on Friday, October 14, 2005
I got some requests on having chat sessions from time to time. Because we didn't searched for a good chat application we are using http://treehouse.ofb.net/chat/ ?lang=en for a first chat test today:
Posted by Michael Schwarz on Tuesday, October 11, 2005
I found a nice implementation for RSA on JavaScript maybe used in a ICryptProvider for Ajax.NET Professional to secure the data is sent from the client-side JavaScript to the server and back. For more details see: http://www.ohdave.com/rsa/ [1]
Posted by Michael Schwarz on Tuesday, October 11, 2005
I read the blog from Rob Chartier [1] and want to show you a feature that is available in Ajax.NET and Atlas. Both libraries are adding debug methods to the client-side JavaScript code.
Posted by Michael Schwarz on Thursday, October 6, 2005
[1]Today I found an article about caching using Ajax.NET. In the article the author said that the Cache object is not working with Ajax.NET. I have done a small example to show how to use the Cache object in AJAX methods.
Posted by Michael Schwarz on Thursday, October 6, 2005
I have uploaded a new pre-build 5.10.6.1 [1] of Ajax.NET Professional that will fix several bugs.
Posted by Michael Schwarz on Thursday, October 6, 2005
I got some requests on how to use inline code with Ajax.NET. Here is a small demo that will get the server time:
Posted by Michael Schwarz on Thursday, October 6, 2005
In some scenarios you will call an AJAX method direct after the window.onload event. The window.onload event will start an asyncronous method and wait for the response. As you can imagine the call will need some milliseconds to get the data back from the server. If you want to have the data available when the page first renderes you can add following code to you Page_Load event.
Posted by Michael Schwarz on Thursday, October 6, 2005