Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It sounds like your assuming 1 HttpHandler = 1 Page or 1 Control, but as I understand, 1 HttpHandler can handle all pages of a certain file extension.</p> <p>Your Question is not very clear, and your reponse to another answerer makes no sense... </p> <p>"In fact, it seemed, to me, a lot like I was asking Http handlers, using a .ajax handler as an example."</p> <p>But I shall assume you are thinking "DocAjaxHander" and "PersonAjaxHandler" should each be created for a "DocAjaxControl" and "PersonAjaxControl" respectively. I dont think that would be neccesary, 1 handler should be able to handle all your ajax requests if you choose to do it that way, but it doesn't feel like the most intuitive solution to me (using HttpHandlers), anyway, onto the details...</p> <p>every IHttpHandler object needs to implement :</p> <pre><code>public void ProcessRequest(HttpContext context) </code></pre> <p>which allows :</p> <pre><code>context.Response.Write("Your JSON Response in here"); </code></pre> <p>but at the level of 'ProcessRequest()', you have no access to the instance of the control which created the ajax call, or to the 'System.Web.UI.Page' object that holds the control, or anything.</p> <pre><code>context.Request </code></pre> <p>to the rescue! With the Request object above you can read QueryStrings, Sessions, an you can determine the path of the original HttpRequest (i.e. PersonAjaxObject may make an ajax call to 'myPersonobjPage.ajax' for its JSON data, but the '.ajax' extention lands the request at your custom http handler and it's ProcessRequest method.)</p> <p>If I was you, and I was going to use an HttpHandler for my ajax calls, I'd use query string data to provide enough info for my handler to know 'what type of object am I responding too' as well as 'what data is that object requesting'.</p> <p>Hope that helps.</p>
    singulars
    1. This table or related slice is empty.
    1. POCustom HttpHandlers and different handler types
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USNnoel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCustom HttpHandlers and different handler types
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for an informative answer, Nnoel. I have actually forgotten what I wanted to achieve when I asked this question, but I didn't want to do a page per entity type thing. I'll clear the question up once I have jogged my memory.
      singulars
      1. PO
      1. USProfK
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload