[fpc-pascal] CustHttpApp and HP httperf tool

[Michael Van Canneyt]

On Tue, 10 Jun 2014, Michael Schnell wrote:

> On 06/10/2014 10:22 AM, Michael Van Canneyt wrote:
>> 
>> The purpose of a websocket is entirely different, these are not 
>> interchangeable technologies.
>> A websocket is not even the HTTP protocol.
> I do know this. I was told that websocket is a kind of successor technology 
> for the replacement of not very "safe" methods like "comet" that rely on 
> kept-open http sockets.

Utter nonsense.

Websockets are good when the server needs to push similar data at high speed, 
no more, no less.

When different request for different kinds of data need to be fetched, 
HTTP 1.1, with its option for keeping the connection open, is more suitable.

>>> If course the browser, the server, and any proxy in between needs to 
>>> support this but I was told that his is supposed to usually to be in 
>>> place.
>> 
>> This is also not correct. I have had many problems deploying a websockets 
>> based program.
>> 
> I see. So what I have been told by a websocket advocate (who indeed 
> erroneously claimed that websocket is a HTTP protocol and proxies would not 
> need to acknowledge such a new protocol, calling me a fool for doubting 
> this), seems to be wrong :-( .

Very wrong. Always distrust advocates :)

Michael.