1999 CA-TennisTrophy – Doubles
Yevgeny Kafelnikov and Daniel Vacek were the defending champions but lost in the first round to Nicolás Lapentti and Marat Safin.
Doubles | |
---|---|
1999 CA-TennisTrophy | |
Champions | |
Runners-up | |
Final score | 6–3, 6–4 |
David Prinosil and Sandon Stolle won in the final 6–3, 6–4 against Piet Norval and Kevin Ullyett.
Seeds
David Adams / John-Laffnie de Jager (First Round) Yevgeny Kafelnikov / Daniel Vacek (First Round) Tomás Carbonell / Jared Palmer (First Round) David Prinosil / Sandon Stolle (Champions)
Draw
Key
- Q = Qualifier
- WC = Wild Card
- LL = Lucky Loser
- Alt = Alternate
- SE = Special Exempt
- PR = Protected Ranking
- ITF = ITF entry
- JE = Junior Exempt
- w/o = Walkover
- r = Retired
- d = Defaulted
First Round | Quarterfinals | Semifinals | Final | ||||||||||||||||||||||||
1 | 63 | 6 | 1 | ||||||||||||||||||||||||
77 | 2 | 6 | 6 | 65 | 6 | ||||||||||||||||||||||
WC | 2 | 2 | 4 | 77 | 4 | ||||||||||||||||||||||
6 | 6 | 77 | 6 | ||||||||||||||||||||||||
3 | 3 | 5 | 63 | 3 | |||||||||||||||||||||||
6 | 7 | 7 | 6 | ||||||||||||||||||||||||
1 | 64 | 5 | 3 | ||||||||||||||||||||||||
6 | 77 | 3 | 4 | ||||||||||||||||||||||||
WC | 4 | 6 | 3 | 4 | 6 | 6 | |||||||||||||||||||||
6 | 1 | 6 | 6 | 2 | 3 | ||||||||||||||||||||||
63 | 77 | 3 | 4 | 4 | 6 | 6 | |||||||||||||||||||||
4 | 77 | 62 | 6 | 4 | 4 | 6 | 77 | ||||||||||||||||||||
WC | 6 | 66 | 64 | 6 | 2 | 65 | |||||||||||||||||||||
4 | 78 | 77 | 6 | 65 | 6 | ||||||||||||||||||||||
Q | 7 | 6 | Q | 2 | 77 | 3 | |||||||||||||||||||||
2 | 5 | 4 |
gollark: As far as I know ISPs can't see that you connect to your own LAN.
gollark: You may only ask dishonest questions.
gollark: VPNs prevent ISPs from seeing all this except possibly to some extent #3, but the VPN provider can still see it, and obviously whatever service you connect to has any information sent to it.
gollark: Anyway, with HTTPS being a thing basically everywhere and DNS over HTTPS existing, ISPs can only see:- unencrypted traffic from programs/services which don't use HTTPS or TLS- the *domains* you visit (*not* pages, and definitely not their contents, just domains) - DNS over HTTPS doesn't prevent this because as far as I know it's still in plaintext in HTTPS requestts- metadata about your connection/packets/whatever- also the IPs you visit, but the domains are arguably more useful anyway
gollark: On my (GNU/)Linux computing devices, which is all of my non-portable ones, I run dnscrypt-proxy, which acts as a local DNS server which runs my queries through DNS over HTTPS/DNS over TLS/DNSCrypt servers.
External links
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.