0

Is it better to create asp.net client control around the component and let it handle talking with the server, querying data, saving data or to use jquery to query the server (and handle responses)?

I am rookie to asp.net, not sure about needed amount of work to achieve similar results to the fully javascript-based solution.

Component is 100% javascript, frequently asks server for data (every 0.5-2 seconds), lets user do some changes, that are later saved by the server, component is hosted as a part of asp.net site. Component queries for just a few types of data / up to 4-5 arguments per query, order of queries is irrelevant. Similar situation with saving data.

Improve this question

2 Answers 2

Reset to default
1

Yes its better to create a ASP.NET composite control and Implement the IScriptcontrol interface.

And then define your JavaScript prototype and use the that for all client operations. These two links gives to fairly through explanation as to how to do it. Basically what you want is already supported by MS and most of the third part controls for ASP.NET are build this way.

Adding Client Capabilities to a Web Server Control

Adding Client Capabilities to a Web Server Control by Using ASP.NET AJAX Extensions

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

1

I think you should create a few prototypes which would handle all the functionality you need. It is of course better, because when you want to create a new request, you will just use your prototype.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.