From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.4
Date: Sun, 06 Dec 2015 14:29:00 -0000 [thread overview]
Message-ID: <87a8pntzua.fsf@Rainer.invalid> (raw)
In-Reply-To: <20151206140852.GB17433@calimero.vinschen.de> (Corinna Vinschen's message of "Sun, 6 Dec 2015 15:08:52 +0100")
Corinna Vinschen writes:
>> VPN access with the worst possible terrestrial roundtrip has been tested
>> for the same case now and goes from 52s to ~1700s or a factor of 33. So
>> roundtrip delay adds an additional factor of about 3, but the server
>> response time seems to play the dominant role even in that scenario.
>
> Uhm... is that good or bad now?!? Do you still think adding this
> functionality is a good idea?
For most of the things I did it worked OK, so I still think AuthZ should
be used.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-12-06 14:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 1:52 Corinna Vinschen
2015-10-23 12:35 ` Achim Gratz
2015-10-23 12:55 ` Corinna Vinschen
2015-10-23 13:10 ` Corinna Vinschen
2015-12-21 13:23 ` Thomas Wolff
2015-12-21 15:01 ` Corinna Vinschen
2015-10-23 14:52 ` Achim Gratz
2015-10-26 11:13 ` Corinna Vinschen
2015-10-26 16:14 ` Achim Gratz
2015-10-27 10:10 ` Corinna Vinschen
2015-10-27 13:28 ` Achim Gratz
2015-10-27 15:11 ` Corinna Vinschen
2015-12-06 9:58 ` Achim Gratz
2015-12-06 14:08 ` Corinna Vinschen
2015-12-06 14:29 ` Achim Gratz [this message]
2015-12-06 19:04 ` Corinna Vinschen
2015-12-06 19:50 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8pntzua.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).