ashx handler performance?

0
0

Hi,

I’m considering using an ashx handler in a wisej app to communicate with MULTIPLE clients over a network.

There could be up 100 or more clients sending their data to the web app handler (and expecting a response back).

The client data packets won’t be huge, perhaps 200 bytes or so, but never-the-less each client will be sending the packet at regular intervals, say every 10 seconds.

Having NO experience with web handlers, I have NO idea of performance or reliability in such a scenario.
Will the handler just work and receive every client request without problems? or will client data clash?

Is this the right method for collecting multiple client data? or should I setup a separate comms. channel, like TCP?

Thanks

Darren

  • Darren
    Hi, Can anyone help? I’m really struggling with this. I’m going around in circles trying to research/find the best method. Web api, MVC, TCP, handlers… etc. It’s driving me up the wall. I can’t seem to even find the recommended method, let alone implement it. Would really appreciate some pointers. Thank you Darren
  • You must to post comments
0
0

Actually, I thought you were implementing a custom handler which need to be registered. But .ashx files don’t need to be registered. I just tried with a self hosted app and the sample ashx added by Visual Studio with Add->New Item->Generic Handler and it works without any registration in web.config with Wisej self hosting.

  • You must to post comments
0
0

The ashx handler is a good solution. See https://msdn.microsoft.com/en-us/library/bb398986.aspx. If you need our professional services we can support you with the specific requirements of your project. I believe Thomas offered to discuss licensing models. He can also discuss other options for training and support.

  • Darren
    Hi Luca, I imagine hardened desktop developers like me are quite frustrating for you guys, & for that I can only apologise. Web dev is completely new to me & perhaps I should be seeking the more general answers elsewhere. What’s worse is I’m experimenting with wisej between other jobs. I performed a simple first test today of a desktop app sending 10,000 webclient posts in a loop to a wisej app. The handler received them all without fault so this method is hopeful & needs to be explored further. However, I ran the web app self-hosted & found the handler no longer worked. I understand this is because of a difference in technology (classic vs integrated pipeline?) I don’t think I can set classic mode via web.config? Can you tell me how this is done? I’m trying to avoid using IIS. Thanks
  • Darren
    Regarding the licensing: During this early stage of proof of concept, I’m just getting a feel for what the future may hold. If I can prove a viable system then the next stage will be a detailed look at costing.
  • Luca (ITG)
    The handlers simply go in a different section in web.config, see https://msdn.microsoft.com/en-us/library/bya7fh0a(v=vs.100).aspx. It’s system.web/httpHandlers. Both can coexist in the same web.config if you turn off validateIntegratedModeConfiguration, see https://docs.microsoft.com/en-us/iis/configuration/system.webserver/validation.
  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.