Home > Back-end >  Written WinnetUrl simulation based on BBS, and how to improve access speed?
Written WinnetUrl simulation based on BBS, and how to improve access speed?

Time:09-18

Through WinnetUrl provides a set of functions, to achieve a more account landing simulation functions of BBS concurrent post, the actual calculation, each account login + posts, around the actual time of 200 milliseconds,
Don't use multithreading, because every time must be after the login process, multithreading: do thread synchronization, time consuming, Don't make thread synchronization easy cause registration number of the chaos, may login validation will fail, just use cycle,

Actual call: when a HttpSendRequest sends first login authentication, followed by a HttpSendRequest is post,

The individual feels is HttpSendRequest contract function a bit time consuming, it is then read after the contract content after returning to the returned!

Dared to have experienced a great god, and what is the method how to make a little faster speed?

CodePudding user response:

I done something like that before.
By cfe or cef is Google browser open source kernel.
Can do cookies isolation.
  • Related