What is the best way to pass Json objects to and from multiple clients for processing by a background task?
I need to have a background task that can process these Json objects on behalf of each client, using a third party API and a common key generated by an initial call to the third party. The key once generated is valid for several hours.
This key is used to allow the third party to process these Json objects and return a response to the background task.
The background task then needs to pass the response back to the client that originally called the background task with the requested Json object(response).
The Client will then modify use the Json object as a basis to create a new Json object and pass it back to the background task for processing by the third party.
NB the key will be invalid if the client calls the third party Api directly.
Many thanks for your help
After much battling this appears to work, question is will it return the right responses to the correct clients?
Many thanks for your help.
How do I set the HttpContext that my Handler requires?
context = HttpContext.Current; Set on the client Page
PPapiHandler obj = new PPapiHandler();
But this does not work because the fields within the context such as the response type cannot be changed by the handler.
I have tried all I can think of. The issue is generating a client context (that can be edited by the ASHX handler), that can be sent to the ASHX Handler so the response is received by the client.
Commands such as context.Response.ContentType = “text/plain”; fail because the HTTP headers are fixed.
As usual there is always a ‘Magic’ part for anything like this that you can’t guess.
The order of events needs to be
The issue is getting the VS generated handler to work by just returning a simple text message to start with.
There is no “synchronized” handler. Every request is passed on a thread – so if you have shared resources your code has to be thread safe. You should simply create an ashx page in your Wisej app or in a separate asp.net app (makes no difference). This is the easiest way and doesn’t require any registration in web.config. Return true for the IsReusable property so only 1 instance is created to handle the requests.
You can save the token in an instance field and retrieve it in a synchronized block (lock block). Don’t worry about the threads, that’s handled by asp.net and the thread pool. You can tweak the thread pool settings in the web.config file, but I’d leave it alone.
The async IHttpAsyncHandler you are referring to doesn’t change anything in terms of requests and threads. All it does is to allow the code in the handler to return the thread to the thread pool when/if it has to wait for another thread to finish, like an external process or an async db request. It doesn’t save threads and doesn’t optimize much.
Wisej uses the IHttpAsyncHandler for the HTTP requests because it allows us to return from the request while suspending the thread when entering the server modal state for modal dialogs.
With 2500 staff registering coming on / off shift at various times of the day at private locations across the country is there not a danger of running out of threads? I thought the aysnc handler made more efficient use of threads.
Does registering the handler as synchronised effectively achieve synchronisation of the token?
Value your thoughts
Looks like I need to create and async hander to cope with the volume. Should be interesting as this is new territory for me!
From the description I don’t think you need a background task. A background task is a thread that executes code and then ends or runs in a loop. It’s not something that is listening to requests. That’s a handler.
I would create an ashx handler and process the requests as they come in. The handler can obtain the key on first use and save it – remember to lock tje block that gets the key. If you mark the handler as reusable, the server will always use the same instance so you don’t even need statics.
It’s basically just a web service.
The JSON objects you refer can be serialized/deserialized as strings. So you are looking for some way to share plain string.
There are several ways to share data among several sessions. Using Wisej you can use a static variable/property as explained in Global Variables thread.
Of course you can use database or some memory based cache like Redis.
Please login first to submit.