In message <[email protected]>, Jesse Wilson writes: > > On Mon, Oct 26, 2009 at 8:26 AM, Oliver Deakin <[email protected]> > wrote: > > > > Jesse Wilson wrote: > > > > > > Wouldn't it be more appropriate to just relax the constraints on > > > hysock_connect_with_timeout? > > > > Sure, what would you suggest? I believe the reason the portlib > > function was implemented this way (only a short 100ms timeout > > maximum) is because on some platforms it is not possible to > > interrupt blocking calls, so once you go into the block there is no > > way to stop it for, for example, VM shutdown. > > We should just put the loop in the platform-specific port! Behavior > on good platforms shouldn't suffer just so we can support crappy > platforms!
+1 That is exactly what I was thinking when I read Oliver's comment. If there is no platform-independent reason for this behaviour then it should be fixed in platform-specific code. -Mark
