World: r4wp

I am expecting that everyone wil now start to scheme!  ( not in the 
Jaime way though )

Andreas has pointed out that the http scheme uses several async handlers, 
and tcp level handler can create events to send to the outer http 
handler :(

So, it gets pretty complicated

Anyone know what Jaime is up to these days? In any case this is great 
stuff Graham.

Just checked LinkedIn, he's working for some company called homeland 
security

Yikes! :-)

Are we talking about Jaime Vargas?

Yes

I still have a couple of his WhyWire wireless units operating on 
a ranch here north of Ukiah.

Have you upgraded the version of rebol running in them?

Great work GrahamC, added to http://rebol.informe.com/wiki/view/R3_network_scheme
 so the community may contribute! :-)

@GrahamC: No, they are still running stock.  Seem to be quite reliable, 
much more so than most access points and wireless bridges out there. 
 They've been running for almost 6 years with no maintenance, and 
both units are outdoors.

That's pretty impressive.  I always wondered what exactly the embedded 
Rebol did in those boxes.

The WhyWire boxes ran OpenBSD off a CF card with Rebol installed. 
 I know Rebol was used at least for configuring the units.  I don't 
know if Rebol actually handled any of the wireless communication 
parts.

It's great to see we've decided to stop "Waiting for Godot". Thanks, 
Ladislav!

I think someone else also had this problem, but I'm getting this 
when building this source on Linux:

undefined reference to `dtoa'

I guess that you did not do make make and make prep?

(that is necessary to include the new source code file)

No, it's not needed for Carl's source

it is needed for this

Thanks, I'll try

Hmm, we need to update the default makefile as well. Thanks for reporting, 
Kaj.

(I solved the conflict with Andreas' change by just taking his makefile)

I'll hold on then

No need to hold, make make will also resolve this.

Kaj, you should not hold, just do what I suggested

Yeah, but I don't want to complicate my build script further. I already 
have to track many branches of REBOL

make make and make prep are already strongly suggested anyway

I try to keep my build procedures as minumal as possible

then I have to wash my hands...

Pardon?

a part of the Easter story...

(no need to understand)

I understand, but I was hoping to update R3 with the minimum fuzz

Pushed an updated makefile.

If Andreas updates the makefile in one of the next commits, my build 
recipe just downloads that. Ah, thanks

However, the reliable way to do a full & clean build is `make make` 
followed by `make clean prep r3`.

All fine now. I've switched the Syllable build system to the community 
source:

http://syllable.cvs.sourceforge.net/viewvc/syllable/syllable/system/apps/utils/Builder/packages/REBOL-Core--current/

Cool.

Kaj, what is the system/version of your build?

2.101.0.4.4 just like Carl's

Hmm, why don't you "force us" to define a new (Syllable) platform?

I'm running on Syllable Server now, so the Linux version is correct

Is your build identical with the 0.4.4?

And because it's not needed. The Linux-configured source - and even 
the binary Linux library - work fine on Syllable Desktop

Do you mean a Syllable Desktop build?

Whichever you are using.

, i.e. if you really get identical builds when getting identical 
system/version