no networking in experimental BeOS REBOL?

[1/6] from: jehamby::anobject::com at: 7-Aug-2000 12:32

Hi, On my PC running BeOS 5.0.1 Pro Edition, I can't get any of REBOL's networking features to work, with either REBOL/core 2.4.24.5.2 or REBOL /view 0.10.18.5.2. For example: REBOL/View 0.10.18.5.2 28-Jul-2000 Copyright 2000 REBOL Technologies. All rights reserved. Type DEMO to run demo if it is disabled

>> read http://anobject.com/

(30 second pause) ** Access Error: Cannot connect to anobject.com. ** Where: read http://anobject.com/ I have BONE Beta 4 installed, but I had the some problem before I installed BONE. Fortunately, the released REBOL/Core 2.3.0.5.2 works properly. Any idea when this will be fixed? Thanks.. -Jake

[2/6] from: rchristiansen:pop:isdfa:sei-it at: 7-Aug-2000 14:49

Jake- I will test this out for you tonight on BeOS 5.0.0 Professional (without beta BONE.) If I recall correctly, I have used the networking features successfully with /View and BeOS 5 Pro. I won't be able to test it, though, until after 7:00 p.m. Central Time U.S. when I get to leave this Windows NT monster and return to my beloved BeOS. -Ryan

[3/6] from: holger:rebol at: 7-Aug-2000 13:05

On Mon, 07 Aug 2000, you wrote:

> Hi, > On my PC running BeOS 5.0.1 Pro Edition, I can't get any of REBOL's

<<quoted lines omitted: 10>>

> installed BONE. Fortunately, the released REBOL/Core 2.3.0.5.2 works > properly. Any idea when this will be fixed?

Works fine here. Same REBOL versions, on BeOS 5.0 Pro, without BONE. Have you checked your network configuration, e.g. DNS, proxies in user.r ? Maybe there is a stale proxy entry somewhere when running 2.4. Are you sure the problem existed before you switched to BONE ? Networking changes from REBOL 2.3 to 2.4 have been fairly minor. The big change from synchronous, blocking network calls to fully asynchronous operation happened between REBOL 2.2 and 2.3. Both 2.3 and 2.4 or BeOS pass our very extensive network tests -- and we used REBOL/BeOS to upload the tar.gz archive to our ftp/web server :-). Btw, is BONE/Beta publically available yet ? Considering the bad shape normal TCP/IP in BeOS is in it would be useful to know if BONE fixes some of the problems... -- Holger Kruse [holger--rebol--com]

[4/6] from: rchristiansen:pop:isdfa:sei-it at: 7-Aug-2000 15:42

BONE is only currently available to beta testers. I have no idea about how to get on the beta testing program. However... Be, Inc., does offer a partner program for developers, but this is mainly for technical support... http://www.be.com/developers/partnerprogram.html You could purchase a BeIA evaluation kit ($95) if you're interested in the internet appliance thing... http://www.be.com/developers/beiaeval.html Or here is the contact info in general... Be, Inc. 800 El Camino Real, Suite 400 Menlo Park, CA 94025 voice: (650) 462-4100 fax: (650) 462-4129

[5/6] from: ssayer:acuson at: 15-Aug-2000 17:14

Similarly, I also have been unable to do any networking with the 0.10.24.4.2 (Linux x86 glibc 6) and the 0.10.25.3.1 (Win32) REBOL/View products myself on a couple of different machines (both with proxy & no proxy configs) which run network code with the release versions just fine (with the exception of the new tcp interface that I can't get to send or receive data connecting even to a telnet port 23 in the manner suggested by the Net docs). I haven't yet looked at it hard enough to tell if it's successfully opening sockets or not (kinda assumed it was known to be broken) but I will now. I'll also have to make sure all these configs are not trying to load my old ftp2 code that works around your SYST bug to ensure that's not the cause too. Later, <SS> On Mon, 7 Aug 2000 [holger--rebol--com] wrote:

[6/6] from: holger:rebol at: 15-Aug-2000 16:51

On Tue, Aug 15, 2000 at 05:14:21PM -0400, [ssayer--acuson--com] wrote:

> Similarly, I also have been unable to do any networking with the > 0.10.24.4.2 (Linux x86 glibc 6) and the 0.10.25.3.1 (Win32) REBOL/View

<<quoted lines omitted: 5>>

> successfully opening sockets or not (kinda assumed it was known to be > broken) but I will now.

There are no new known problems (known to us, anyway) in the networking code in any of the experimental versions, with the exception of BeOS. The problem with the BeOS version is caused by a bug in BeOS: the apparently working non-blocking connect() function in BeOS actually has race conditions that are not reproducable on our machines, but happen for some users. We will switch back to normal non-blocking connect()s in the next experimental build (with the unpleasant side effect that you cannot interrupt a connection in progress with the Escape key -- same behavior as REBOL 2.2 everywhere and REBOL 2.3 BeOS). If you find any other reproducable problems please send reports to helpdesk, and if possible provide examples we can run on our machines. Regarding connections to telnet port 23: this is probably a bad example, because telnet (and rlogin) are exceptions in that they make use of TCP urgent mode , so a fully compliant telnet client cannot be written in most high-level languages. It requires getting "down and dirty" into the depths of the TCP C socket API... Try connecting to any other server (smtp, nntp, http or anything else). -- Holger Kruse [holger--rebol--com]

Notes

Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted