Re: [josm-dev] IPv6 problems

2016-01-02 Thread Florian Lohoff
On Fri, Jan 01, 2016 at 09:12:50PM +0100, Dirk Stöcker wrote: > On Fri, 1 Jan 2016, Philip Homburg wrote: > > >- Ideally, operating systems should ship with a happy eyeballs implementation > > in the C library. I don't know any that does. It is not such a great idea > > for applications to roll

Re: [josm-dev] IPv6 problems

2016-01-02 Thread Florian Lohoff
On Fri, Jan 01, 2016 at 02:03:57PM +0100, Dirk Stöcker wrote: > On Fri, 1 Jan 2016, Florian Lohoff wrote: > > >Currently josm tries to be clever and either does v6 or v4 and tries > >to detect whether the host is v6 enabled. This is broken by design. > >You cant detect whether you will be able to

[josm-dev] DNS timeout/fail on startup Was: IPv6 problems

2016-01-02 Thread Florian Lohoff
On Fri, Jan 01, 2016 at 02:03:57PM +0100, Dirk Stöcker wrote: > I also don't believe that's a JOSM issue, as JOSM does not remember > any states between connections. Maybe your connection is simply to > slow and you need to increase the timeouts so it works for your > system. JOSM uses reasonable

Re: [josm-dev] DNS timeout/fail on startup

2016-01-02 Thread Dirk Stöcker
On Sat, 2 Jan 2016, Florian Lohoff wrote: Just let the very first DNS request for josm.openstreetmap.org fail/timeout - You get a popup "Network errors occured" and "Change proxy setting". This is abolute nonesense. I dont use any proxy - A simple DNS query failed - Thats life. I might even be

Re: [josm-dev] How to ask for confirmation at layer deletion or exit?

2016-01-02 Thread Holger Mappt
If we never ask for confirmations then you would be able to quit JOSM while it has modified data. There can be no notice about saved changes at that point. The earliest time to display that notice would be the next JOSM start. But the data might have changed on the server in the meantime. In

Re: [josm-dev] How to ask for confirmation at layer deletion or exit?

2016-01-02 Thread Martin Koppenhoefer
sent from a phone > Am 01.01.2016 um 21:37 schrieb Russ Nelson : > > Never ask for confirmations. It's never the right thing to do unless > you're very short of resources, which we never are these days. that's not exactly true, you can always come to the limits, especially

Re: [josm-dev] IPv6 problems

2016-01-02 Thread Simon Legner
Hi all, what about an expert (for now) option (such as prefer.ipv6=jvm) to disable JOSM's algorithm completely and solely rely on the JVM to figure out the correct way to connect to a server? According to [1] … > IPv6 in Java is transparent and automatic. Porting is not necessary; there is > no

Re: [josm-dev] IPv6 problems

2016-01-02 Thread Dirk Stöcker
On Sat, 2 Jan 2016, Simon Legner wrote: what about an expert (for now) option (such as prefer.ipv6=jvm) to disable JOSM's algorithm completely and solely rely on the JVM to figure out the correct way to connect to a server? According to [1] … IPv6 in Java is transparent and automatic. Porting

Re: [josm-dev] IPv6 problems

2016-01-02 Thread Simon Legner
On Sat, Jan 2, 2016 at 11:26 PM, Simon Legner wrote: > what about an expert (for now) option (such as prefer.ipv6=jvm) to > disable JOSM's algorithm completely and solely rely on the JVM to > figure out the correct way to connect to a server? I checked the code: This

Re: [josm-dev] IPv6 problems

2016-01-02 Thread Dirk Stöcker
On Sun, 3 Jan 2016, Simon Legner wrote: On Sat, Jan 2, 2016 at 11:26 PM, Simon Legner wrote: what about an expert (for now) option (such as prefer.ipv6=jvm) to disable JOSM's algorithm completely and solely rely on the JVM to figure out the correct way to connect to a