ihttphandler

问题 Created a custom handler and behaves as my title states, but I need parallel processing of requests. This handler asks to a second machine for html content, images and other web page related content. But as every request gets kind of "queued" the result is a very slow response of content. Web browsers are able to send multiple requests at the same time, but this "problem" reduces it to a single request. I've verified this behavior logging the begging and ending of the handler. Never a request

问题 Created a custom handler and behaves as my title states, but I need parallel processing of requests. This handler asks to a second machine for html content, images and other web page related content. But as every request gets kind of "queued" the result is a very slow response of content. Web browsers are able to send multiple requests at the same time, but this "problem" reduces it to a single request. I've verified this behavior logging the begging and ending of the handler. Never a request

问题 I am developing a custom HttpHandler, to do so I write a C# Class Library and compile to DLL. As part of this I have some directory locations which I want not hard coded in the app, so i'm trying to put it in the app.config which I've used before. Before this has worked by just going building the app.config: <?xml version="1.0" encoding="utf-8" ?> <configuration> <appSettings> <add key="Share" value="C:\...\"/> </appSettings> </configuration> And then obtaining this in code like: var

问题 Simple task like make AJAX request , pass one parameter and return result, can be done with Web Service and IHttpHandler, so where is the difference ? 回答1: ASP.NET web services are in fact a type of HttpHandler that provide an XML based communication infrastructure based on W3C standards (SOAP/WSDL). This means that non .NET clients can interoperate with ASP.NET web services. In your case where you're making a very simple single ajax request to return a simple result, ASP.NET/XML web services

问题 Consider a Web.config file containing the following httpHandlers declaration: <httpHandlers> <add verb="*" path="*" type="MyWebApp.TotalHandlerFactory"/> </httpHandlers> In other words, this handler factory wants to “see” all incoming requests so that it gets a chance to handle them. However, it does not necessarily want to actually handle all of them, only those that fulfill a certain run-time condition: public sealed class TotalHandlerFactory : IHttpHandlerFactory { public IHttpHandler

问题 usually, when I look at a ASP.Net MVC application, the Route table gets configured at startup and is not touched ever after. I have a couple of questions on that but they are closely related to each other: Is it possible to change the route table at runtime? How would/should I avoid threading issues? Is there maybe a better way to provide a dynamic URL? I know that IDs etc. can appear in the URL but can't see how this could be applicable in what I want to achieve. How can I avoid that, even

问题 When writing a http handler/module, there is an interface member to implement called - bool IsReusable. What is the significance of this member? If I set it to false (or true), what does this mean for the rest of the web app? 回答1: The normal entry point for a handler is the ProcessRequest method. However you may have code in the class constructor which puts together some instance values which are expensive to build. If you specify Reusable to be true the application can cache the instance and

问题 I'm writing a IHttpHandler and I'll need to implement a IsReusable property. When I look at the MSDN documentation it says: Gets a value indicating whether another request can use the IHttpHandler instance. This isn't very helpful. In which situations should I use a reusable handler and in which situations should it not be reusable? Follow up questions: What is reuse? Can I maintain state (i.e. class variables) when Reusable = true ?? 回答1: This property indicates if multiple requests can be

问题 I'm stuck in an Async deadlock and I can't figure out the correct syntax to fix it. I've looked at several different solutions, but can't seem to quite figure out what is causing the problem. I am using Parse as a backend and trying to use a handler to write to the table. My handler looks something like: public class VisitorSignupHandler : IHttpHandler { public void ProcessRequest(HttpContext context) { //Get the user's name and email address var UserFullName = context.Request.QueryString[

问题 I have an ASP.NET application and dll which extends IHttpModule. I have used the below method to save the session variables in httpcontext through public class Handler : IHttpModule,IRequiresSessionState { public void Init(HttpApplication httpApp) { httpApp.PreRequestHandlerExecute += new EventHandler(PreRequestHandlerExecute); } public void PreRequestHandlerExecute(object sender, EventArgs e) { var context = ((HttpApplication)sender).Context; context.Session["myvariable"] = "Gowtham"; } }