setting DatagramSocket.setSoTimeout() seems to have no effect
The group you are posting to is a
Usenet group . Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
From:
xtrawurst <rafael.Spr... @web.de>
Date: Fri, 7 Dec 2007 04:56:40 -0800 (PST)
Local: Fri, Dec 7 2007 7:56 am
Subject: setting DatagramSocket.setSoTimeout() seems to have no effect
Hey,
no matter which value I pass when I call setSoTimeout(int millisecs)
on my DatagramSocket, the receive() call always blocks forever if
there is no data available. Is there anyone experiencing the same
behaviour? Or has anyone got this to work?
You must
Sign in before you can post messages.
You do not have the permission required to post.
From:
dave <Dayong... @gmail.com>
Date: Fri, 7 Dec 2007 06:56:59 -0800 (PST)
Local: Fri, Dec 7 2007 9:56 am
Subject: Re: setting DatagramSocket.setSoTimeout() seems to have no effect
> setSoTimeout(int millisecs)
I would prefer Google Android Dev Team change the method name to
"setSocketTimeout".
You must
Sign in before you can post messages.
You do not have the permission required to post.
From:
"Luisa Magarian" <magar... @google.com>
Date: Fri, 7 Dec 2007 12:42:15 -0800
Local: Fri, Dec 7 2007 3:42 pm
Subject: Re: [android-developers] Re: setting DatagramSocket.setSoTimeout() seems to have no effect
Hi Dave and xtrawurst,
Thank you for the report and suggestion. I've logged the issue for you.
Thanks, Luisa
On Dec 7, 2007 7:12 AM, xtrawurst <rafael.Spr... @web.de> wrote:
> I would prefer Google Android Dev Team to implement the method ;)
> On Dec 7, 3:56 pm, dave <Dayong... @gmail.com> wrote: > > > setSoTimeout(int millisecs)
> > I would prefer Google Android Dev Team change the method name to > > "setSocketTimeout".
You must
Sign in before you can post messages.
You do not have the permission required to post.
From:
Kabe <kabr... @gmail.com>
Date: Fri, 11 Jan 2008 22:33:54 -0800 (PST)
Local: Sat, Jan 12 2008 1:33 am
Subject: Re: setting DatagramSocket.setSoTimeout() seems to have no effect
+1 for this, wanted to point out that Socket.connect() that takes a
timeout also does not work correctly, it always blocks for 190sec no
matter what timeout value you set. Is this also a known issue? and
should we expect it fixed in the next SDK release?
On Dec 8 2007, 4:42 am, "Luisa Magarian" <magar... @google.com> wrote:
> Hi Dave and xtrawurst,
> Thank you for the report and suggestion. I've logged the issue for you.
> Thanks,
> Luisa
> On Dec 7, 2007 7:12 AM, xtrawurst <rafael.Spr... @web.de> wrote:
> > I would prefer Google Android Dev Team to implement the method ;)
> > On Dec 7, 3:56 pm, dave <Dayong... @gmail.com> wrote:
> > > > setSoTimeout(int millisecs)
> > > I would prefer Google Android Dev Team change the method name to
> > > "setSocketTimeout".
You must
Sign in before you can post messages.
You do not have the permission required to post.
From:
Kyara11 <kyara5... @gmail.com>
Date: Sat, 12 Jan 2008 14:58:25 -0800 (PST)
Local: Sat, Jan 12 2008 5:58 pm
Subject: Re: setting DatagramSocket.setSoTimeout() seems to have no effect
Hi Luisa,
Please also help check this. After I call setSoTimeout() on a
DatagramSocket, I always get java.lang.ClassCastException when I want
to read the timeout value back, eg., by calling
int to=dramSocket.getSoTimeout().
It is a simple operation which seems not easy to be mistaken, isn't
it?
Thank you in advance!!
Kyara
On Dec 7 2007, 12:42 pm, "Luisa Magarian" <magar... @google.com> wrote:
> Hi Dave and xtrawurst,
> Thank you for the report and suggestion. I've logged the issue for you.
> Thanks,
> Luisa
> On Dec 7, 2007 7:12 AM, xtrawurst <rafael.Spr... @web.de> wrote:
> > I would prefer Google Android Dev Team to implement the method ;)
> > On Dec 7, 3:56 pm, dave <Dayong... @gmail.com> wrote:
> > > >setSoTimeout(int millisecs)
> > > I would prefer Google Android Dev Team change the method name to
> > > "setSocketTimeout".
You must
Sign in before you can post messages.
You do not have the permission required to post.