Sponsored Content
Full Discussion: UNIX.com response times
Contact Us Post Here to Contact Site Administrators and Moderators UNIX.com response times Post 303005614 by bakunin on Friday 20th of October 2017 07:13:00 AM
Old 10-20-2017
Update: here is a document explaining why HTTPS is faster than HTTP.

It boils down to a Google-developed additional session layer (SPDY) from which only HTTPS profits. Basically it is not HTTPS vs. HTTP but multiplexed sessions over a single TCP connection versus unmultiplexed sessions. It would be possible to do HTTP over SPDY too (it is just not done). HTTP2 is basically SPDY standardised and further developed.

In principle HTTP is slightly faster than HTTPS: there are caching facilities so that not every retransmission has to be originated by the client. HTTPS lacks that because relaying stations cannot read what they transmit.

How SPDY speeds up things is especially via the session multiplexing. This gains lots of time because of the delayed TCP-ack, which takes 500ms.

bakunin
These 4 Users Gave Thanks to bakunin For This Post:
 

5 More Discussions You Might Find Interesting

1. Programming

Problem with implementing the times() function in C (struct tms times return zero/negative values)

Hello, i'm trying to implement the times() function and i'm programming in C. I'm using the "struct tms" structure which consists of the fields: The tms_utime structure member is the CPU time charged for the execution of user instructions of the calling process. The tms_stime structure... (1 Reply)
Discussion started by: g_p
1 Replies

2. Shell Programming and Scripting

feasibility of opening a website link from unix and get a response in the form of xml or html

i just wanted to know whether is it possible to open a website link and get a response in the form of xml or html format... the website is of local network... for example something like this wget http://blahblah.samplesite.com/blachblahcblach/User/jsp/ShowPerson.jsp?empid=123456 ... (2 Replies)
Discussion started by: vivek d r
2 Replies

3. Red Hat

Response Times

Hello all. Let me qualify my question by saying that I am struggling with how to ask the question I am semi green but have no issue reading up if pointed in the right direction. Please be gentle! A RHEL server 6.2. Hosts a statistical application that has some web apps and batch programming... (0 Replies)
Discussion started by: rsheikh01
0 Replies

4. What is on Your Mind?

Changing Times at UNIX.COM

Over the past year, I have written so much code at UNIX.COM, I've gained 4 KGs just sitting at my desk and not exercising! However, it seems that "no good deed goes unpunished" and not only have I sacrificed my health (gaining weight, not exercising as much), but there is also my family who is... (4 Replies)
Discussion started by: Neo
4 Replies

5. Shell Programming and Scripting

Choosing VPN server based on server response times

Hello all, I am using the VPN provider Private Internet Access. I am using the Raspberry Pi 4 with 4GB of RAM, performance on this upgraded board is great. Anyways I am connecting to its service using systemd's openvpn-client @ US_New_York_City.service I wonder if I can create a... (5 Replies)
Discussion started by: haloslayer255
5 Replies
Net::DRI::Transport::HTTP(3pm)				User Contributed Perl Documentation			    Net::DRI::Transport::HTTP(3pm)

NAME
Net::DRI::Transport::HTTP - HTTP/HTTPS Transport for Net::DRI DESCRIPTION
This module implements an HTTP/HTTPS transport for establishing connections in Net::DRI METHODS
At creation (see Net::DRI "new_profile") you pass a reference to an hash, with the following available keys: timeout time to wait (in seconds) for server reply https_debug https_version https_cert_file https_key_file https_ca_file https_ca_dir all key materials for https access, if needed remote_url URL to access client_login client_password protocol login & password client_newpassword (optional) new password if you want to change password on login for registries handling that at connection protocol_connection Net::DRI class handling protocol connection details. Specifying it should not be needed, as the registry driver should have correct default values. protocol_data (optional) opaque data given to protocol_connection class. For EPP, a key login_service_filter may exist, whose value is a code ref. It will be given an array of services, and should give back a similar array; it can be used to filter out some services from those given by the registry. verify_response (optional) a callback (code ref) executed after each exchange with the registry, being called with the following parameters: the transport object, the phase (1 for greeting+login, 2 for all normal operations, 3 for logout), the count (if we retried multiple times to send the same message), the message sent (HTTP::Request object) and the response received (HTTP::Response object). This can be used to verify/diagnose SSL details, see example in file t/704opensrs_xcp_live.t local_host (optional) the local address (hostname or IP) you want to use to connect (if you are multihomed) SUPPORT
For now, support questions should be sent to: <netdri@dotandco.com> Please also see the SUPPORT file in the distribution. SEE ALSO
<http://www.dotandco.com/services/software/Net-DRI/> AUTHOR
Patrick Mevzek, <netdri@dotandco.com> COPYRIGHT
Copyright (c) 2008-2010 Patrick Mevzek <netdri@dotandco.com>. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. See the LICENSE file that comes with this distribution for more details. perl v5.10.1 2010-03-25 Net::DRI::Transport::HTTP(3pm)
All times are GMT -4. The time now is 08:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy