On Wed 05 Dec 2007 19:09, Kalle Valo <[EMAIL PROTECTED]> writes: > "ext Tomi Ollila" <[EMAIL PROTECTED]> writes: > >> So I remember incorrectly -- the real reason is (probably) that when >> socket(2) system call is started, these Internet Tablets tries to make >> internet connection up (either via wlan, or bt-connected phone....) >> and if that cannot be made, socket(2) fails. >> There is no way knowing at socket(2) time that user wants to connect(2) >> 127.0/8 addresses. There is probably good reason to wrap socket() instead >> of connect(), bind() (and some other system calls.. timeouts maybe...). > > Nope, any of the calls you mentioned are not modified (or wrapped) in > any way. They work similarly in Nokia tablets as in normal Linux PCs. > > In tablets applications request connections through libconic and after > that they can open sockets as usual. If some applications request > connections to localhost from libconic, that's a bug in the > application, not in lower levels.
OK! So next the big question: If I open default browser and try to connect http://127.0.0.1/ and I have application in port 80 serving http requests should that work? (with all / which IT OS versions?) > Exception: there was a preload library (which name I don't even > remember anymore) in osso-ic-lib which wrapped socket() and close() > functions and did just what you described here. But I doubt (and hope) > that nobody uses it anymore. What is someone wants to take some unix software, compile it unmodified for internet tables and expect it to make internet connections as the browser does now (i.e. automatically start connection over wlan/bt) ? > -- > Kalle Valo Thanks, Tomi _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
