![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | Best way to implement a high performance: HTTP messaging engine I am developing a high performance HTTP messaging engine which potentially needs to service many simultaneous requests. My main concern with using any of the built in framework classes such as WebClient or HttpWebrequest is that they internally use threads from the machines thread pool which I think potentially limits scalability. Can anyone offer advice on how best to implement a scalable HTTP messaging engine? I know going back to basics and building a HTTP messenger upwards from the TCP level would be the best solution but this seems like a fairly substantial coding task. Ideally I would like to leverage something at a little higher level. I've done a fair bit of Googling but cannot find a definitive answer. Any ideas, tips or advice would be gratefully received. Clive __________ Information from ESET NOD32 Antivirus, version of virus signature database 4473 (20091001) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com |
My System Specs![]() |
| | #2 (permalink) |
| | Re: Best way to implement a high performance: HTTP messaging engine Windows Azure "C Smith" <nomail@newsgroup> wrote in message news:uYenBasQKHA.1372@newsgroup Quote: >I am developing a high performance HTTP messaging engine which potentially >needs to service many simultaneous requests. > > My main concern with using any of the built in framework classes such as > WebClient or HttpWebrequest is that they internally use threads from the > machines thread pool which I think potentially limits scalability. > > Can anyone offer advice on how best to implement a scalable HTTP messaging > engine? I know going back to basics and building a HTTP messenger upwards > from the TCP level would be the best solution but this seems like a fairly > substantial coding task. Ideally I would like to leverage something at a > little higher level. > > I've done a fair bit of Googling but cannot find a definitive answer. > > Any ideas, tips or advice would be gratefully received. > > Clive > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 4473 (20091001) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Performance Low-Cached Memory High | Vista performance & maintenance | |||
| Really weird issue when NOT in high performance mode | General Discussion | |||
| TCP High Performance Test Failed | Network & Sharing | |||
| My company blocks MSN messaging or any instant messaging at work | Live Messenger | |||
| Performance gains with a high end graphics card | Vista General | |||