World: r3wp

ahh... working sessions .. sweet

pioneer with arrow in back?

Funny as that would be, let's try to stay positive...

bwaaaahh

:P

the idea being conveyed is how a simpler technology ( arrow) can 
be more nimble in some situations than a more advanced technology 
( guns )

So, we construct an ideogram around that.

An arrow shot into a gun barrel, like you see in Green Arrow comics 
all the time?

How about a tent ... lightweight website home

easily stylized and non violent

Whatever tent style the Cheyenne used...

Thank you guys for your interesting propositions ;-)

Brian, don't worry, I won't spend much time on that. Btw, thanks 
for the cheerleading !

I think a tent is pretty close to ideal ...

Although other nomadic cultures used tents, they are mostly associated 
with the Indian nations

It's portable and easily setup .. a feature of Cheyenne

Looks like it fits well the concept.

and like most websites ..it's a home under construction :)

I don't know, but a "powered by" integrated over the current Cheyenne 
logo would be
fine by me...well that, and a transparent background.

powered by a tent

Hosted in a tent. Good point though.

Linux is like a wigwam?^^

This weekend is nearly finished for me ... any chance of Cheyenne 
being released soon?

It's early sunday here, I've just woke up, I need the whole day to 
finish the doc and make the release.

Ok.

Don't spend too much time on the logo :)

;-)

I have to delay the Cheyenne release by one day due to numerous issues 
today while running it on Linux. Among these issue are rebol crashing 
bugs on linux (like mold/all/flat, listed on RAMBO).

if you don't use flat, it doesn't crash. pretty simple. (I was the 
reporter)

Yes, Henrik, I saw that after spending almost one hour trying to 
figure out why was encapped Cheyenne crashing with segfault on some 
requests...

Just a few words to say that thanks to Will, I've managed to fix 
an important issue regarding port leaking in Cheyenne, and we even 
patched Will's server in live without having to reboot Cheyenne (kind 
of open heart surgery). The new release is almost ready, but I'm 
late with the documentation and website update, so I guess that I'll 
make a first release here for the people already using it and make 
a public release on the website with documentation (and logos for 
btiffin ;-)) on wednesday night.

A brand new bugtracker (in RSP) will be online by the end of the 
week, so I'll be able to track more easily and reliably all issues 
regarding Cheyenne and any other of my projects.

The bugtracker will be fully open sourced and will also serve as 
demo of a complete online application done in RSP with a DB backend 
(MySQL currently).

cool

I'd say GREAT! the live patching was a real adrenaline experience 
8-))

great news.

I always love your work :)

Love it!

Look forward to your new release. Keep up the good work!

Thanks you all, guys, for your enthusiasm! :-)

looking forward to trying it. will Cheyenne be R2 only?

So RSP and sessions are already working? That's cool! Top quality 
http server which does not need to be installed!

And I am loooking forward to compare Cheyenne R2 vs Cheyenne R3 (using 
threads), and to see speed, and system resources requirements :-)

about R2, have an ajax app with db calls (ok mysql +query cache enabled) 
, 200 reqs/sec brings a dualG5 2GHz at 80% cpu pretty fast 8-)

isn't 200 req/sec job for some server, than desktop machine? ;-)

ah, misplace RSP with RPC, heh :-) RSP - typical old model :-)

now that Cheyenne is ultrastable on heavy traffic, I'm more looking 
forward to a Intel native rebol for os x running on a 8core xserve 
than a R3 version ;-)

why? Shouldn't R3 be just more async and shouldn't threading be there 
to provide us with better scaling?

btw - could I do following? Set my .html files to be treated as CGI, 
via some handler? I can't stand using mixing templates with html 
codes, especially in that manner, where your template code ruins 
normal browser display ....

still looking forward to a faster R3 version, shouldn't be to hard 
to add machines and distribute task-handlers , and if the main process 
get too busy, put a lighthttpd proxy in front.