Well, glad you asked
Actually, there are quite a few added benefits, but I'll just highlight
my favorite. With all other callback libraries (including ASP.NET 2.0's
calback support) the only thing that is implemented is the callback
itself. It is still up to the developer to hook up the client side
event to raise the callback, to implement the server-side function that
is raised, and to handle the response on the client-side. If any DHTML
updating needs to be performed, the developer has to write the
JavaScript.
With our product, the ONLY code you write is server-side code. We take
care of writing any required JavaScript. For example.say you wanted to
write a test app that, when a user clicked a button, a drop-down list
was filled. Of course, this would need to occur seamlessly...without a
refresh.
With our product, simply drag a LiveButton and LiveDropDownList on the
WebForm, implement the click event, and within the event, rebind the
LiveDropDownList to the new data. We take care of raising the callback
and of sending back the appropriate JavaScript to fill the drop-down.
Private Sub LiveButton_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles LiveButton.Click
LiveDropDownList.DataSource = GetDataSource()
LiveDropDownList.DataBind()
End Sub
....and you're done!
Now, go ahead and write the equivalent using Ashley or ASP.NET 2.0
callback libraries, and you'll begin to see the difference.
Anyway, for most simple callback scenarios, the Ashley or ASP.NET 2.0
callback support may be enough for you. In that case, use it by all
means! However, if you need more advanced support you may want to
consider using our product. There is a free 30-day, full trial to see
if it will save you development time.
