1

Topic: WebForm vs MVC

Good afternoon!
It is necessary to describe a problem to the developer of the WebForm-appendix:
Problem in that the WebForm-appendix hangs up time from time.
The operator gives request (pushes the button on the form) and the site hangs up.
In multi-threaded ASP.NET MVC such problems are not present (I develop).
I so understand that the WebForm-appendix waits for the previous answer (for example sent on ) from the server and does not allow to fulfill action of the operator.
In MVC with "public async Task <>" to the browser the answer from the server comes, what he would not wait and allowed to fulfill following actions?
I ask the help at knowing in a substantiation of a problem of hangup of one-continuous WebForm-appendices.

2

Re: WebForm vs MVC

potkin;
Well can at you there fat  chases.
Describe that on network activity thus, what broad gulls on a server thus.
The item with. Your concept of a multithreading  async not the true.

3

Re: WebForm vs MVC

potkin wrote:

and the site hangs up.

it that means? Application a server web ceases to work before restarting of the server or what?
What is "the one-continuous web application" in your understanding?

4

Re: WebForm vs MVC

potkin wrote:

In MVC with "public async Task <>" to the browser the answer from the server comes, what he would not wait and allowed to fulfill following actions?

and if to write without async, the web application becomes one-continuous your way? No

5

Re: WebForm vs MVC

WebForm application not mine.
If briefly:
1)
For example, to launch any abrupt request.
To open the second tab of the browser of Chromium with the same address of a site.
The second tab will press, the first tab yet does not fulfill. And only after that displays page
2)
Well and a real example:
The operator pushes the button on page - the tab of the browser of Chromium does not answer (is twisted , the pier request is sent, I look forward to hearing).
And so can proceed and 5 and 10 minutes.
I take I close the browser.
I rediscover and launch  the task. Fulfills quickly.
But, after a while again the problem repeats.
Here the problem in the browser, it waits for end of the previous request.
I once wrote for a long time WebForm-appendices and often faced such problem.
Then passed on MVC and such problem disappeared.

6

Re: WebForm vs MVC

I should describe a problem .
As it correctly to make

wrote:

the item with. Your concept of a multithreading  async not the true.

Not correctly expressed or can something I do not know.
I will not argue, but in asynchronous MVC such problems and close are not present.

wrote:

it that means? Application a server web ceases to work before restarting of the server or what?

Before browser restarting

wrote:

That such "the one-continuous web application" in your understanding?

The asynchronous?

7

Re: WebForm vs MVC

potkin wrote:

It is necessary to describe a problem to the developer of the WebForm-appendix:

potkin wrote:

I Ask the help at knowing in a substantiation of a problem of hangup of one-continuous WebForm-appendices.

The programmer?
Make the test application for 5. Also deliver there sleep for 5 minutes
Then repeat the test with tabs.
Since can brake from one million reasons.

8

Re: WebForm vs MVC

potkin wrote:

For example to launch any abrupt request.
To open the second tab of the browser of Chromium with the same address of a site.
The second tab will press, the first tab yet does not fulfill. And only after that you displays page

Well generally outputs made absolutely left.
Simple example - as a result of your request the table in a DB was blocked, will not be unblocked yet, other request expects access appearance to a DB. This in no way does not concern to  generally, these are curve hands of the developer.
But as the situation at you is played perfectly back, it is safely possible

potkin wrote:

it is just necessary to describe a problem .

it is not necessary to finish thinking anything, let he tests

9

Re: WebForm vs MVC

potkin wrote:

I should describe a problem .

He that speaks on brakes?
Simply show it  a case with tabs.
Or beer together to drink))).

10

Re: WebForm vs MVC

wrote:

the table in a DB

was blocked
1.
Lifted locally old "mega" the project on Web forms.
Made too most and the second tab waits yet the first does not fulfill.
There there are no records in a DB, only Selekt.
2.
And on the new project (rewrote old WebForm on MVC) launched the same request.
The second tab without problems opened, thus the first yet did not fulfill.
THE ITEM WITH.
During an era of Web forms this problem arose time and again and about it wrote much.
But, now, with arrival , the problem departed also these articles are not actual...
But, I still will rummage in Google can  as I will expose here...

11

Re: WebForm vs MVC

potkin wrote:

Made too most and the second tab waits yet the first does not fulfill.

check up by two parallel machines instead of tabs.
?

12

Re: WebForm vs MVC

potkin wrote:

rewrote old WebForm on MVC

I suspect that you  want to force to rewrite the project as you earlier).
But it is not enough arguments.

13

Re: WebForm vs MVC

wrote:

check up by two parallel machines instead of tabs.

Here a problem in the browser!
It is necessary by one machine and in one browser to open some tabs and that they would not wait, while the previous tab for the same address of a site fulfills.
THE ITEM WITH.
Even if to open on one PC in different browsers all fulfills instantly.
And here in one - waits while fulfills request about one of tabs and only then displays page on the second tab.

14

Re: WebForm vs MVC

potkin;
Agree that you completely replaced a question of a subject of a topic declared in the beginning).
Good luck!

15

Re: WebForm vs MVC

>>> the Problem that the WebForm-appendix hangs up time from time.
, it was necessary to write a site  a site at the operator, instead of the web application.

16

Re: WebForm vs MVC

potkin wrote:

the request is sent, I look forward to hearing).
And so can proceed and 5 and 10 minutes.

What for to do requests with the answer 5?

17

Re: WebForm vs MVC

It probably is somehow connected to it:

wrote:

the Maximum quantity of simultaneous constant connections by default for the server/proxy:
Firefox 2: 2
Firefox 3 +: 6
Opera 9.26: 4
Opera 12: 6
Safari 3: 4
Safari 5: 6
IE 7: 2
IE 8: 6
IE 10: 8
Chrome: 6

18

Re: WebForm vs MVC

wrote:

What for to do requests with the answer 5?

No, pushed the button on a site, the tab sends request and the answer of 5 minutes waits.
But, if I close and I open the browser the request fulfills instantly.

19

Re: WebForm vs MVC

potkin wrote:

It probably is somehow connected to it:

F12 push. There it is visible that  brakes at the front.
On  broad gulls and monitoring.

20

Re: WebForm vs MVC

potkin wrote:

WebForm application not mine.
If briefly:
1)
For example, to launch any abrupt request.
To open the second tab of the browser of Chromium with the same address of a site.
The second tab will press, the first tab yet does not fulfill. And only after that displays page
2)
Well and a real example:
The operator pushes the button on page - the tab of the browser of Chromium does not answer (is twisted , the pier request is sent, I look forward to hearing).
And so can proceed and 5 and 10 minutes.
I take I close the browser.
I rediscover and launch  the task. Fulfills quickly.
But, after a while again the problem repeats.
Here the problem in the browser, it waits for end of the previous request.
I once wrote for a long time WebForm-appendices and often faced such problem.
Then passed on MVC and such problem disappeared.

Similar on that is actively used Session. On it lock for the period of the request is superimposed, here the second request and waits, while it does not release.
Ask the programmer not to use Session there where it is not required.

21

Re: WebForm vs MVC

potkin wrote:

it is passed...
Here a problem in the browser!
It is necessary by one machine and in one browser to open some tabs and that they would not wait, while the previous tab for the same address of a site fulfills.
THE ITEM WITH.
Even if to open on one PC in different browsers all fulfills instantly.
And here in one - waits while fulfills request about one of tabs and only then displays page on the second tab.

So because in different browsers of session different and they are not locked.

22

Re: WebForm vs MVC

skyANA wrote:

Ask the programmer not to use Session there where it is not required.

smile)) And the way hangs up a label over the monitor: sessions - angrily

23

Re: WebForm vs MVC

hVostt;
Early. The reason yet did not find.
Can hands curves.

24

Re: WebForm vs MVC

Petro123 Precisely not a bot?

25

Re: WebForm vs MVC

love_bach wrote:

Petro123 it is exact not a bot?

to us very important your judgement.