World: r3wp

server-side stuff for huge traffic sites? I thought you were in the 
qtask team

In theory it would by possible to make an extension that could implement 
the /Library dialect, or a better version of it.

Salaried: Yes, on occasion. In the Qtask team: Not since mid-May.

doc, on windows, its easy because we can load and map functions on 
demand.  the only complexity is to build a proper structure dialect.

This is way off topic - switching somewhere better.

I was looking at using some of the windows speech recognition stuff 
via /library  earlier today. Accept voice prompts, and push to a 
web page via sockets.

Playing with PowerShell for the first time as well.  Has some promise.
The speech recognition in Windows 7 is world class.

R3 as an academic white paper is great. But I've learned that building 
stuff nobody wants is a waste of life. (Paul Graham agrees)

Without R3 being completely open source, in this day and age, is 
soo 1984. And if the 'killer app' is a webserver, and that web server 
doesn't plan on using R3, then it's not much more than a hobby.
But hey, nothing wrong with having a hobby.

( "it" being R3 of course!

http://huddledmasses.org/control-your-pc-with-your-voice-and-powershell/

Doc, is there a binary for the latest Cheyenne that works with curecode?

James: no, but I'll probably make a few ones today so people can 
test lastest CureCode easily. What OS are you using?

Terry: fully open sourcing R3 and using a dual licensing (GPL + commercial), 
as a lot of other small companies do, seems to me like the only viable 
model when you don't have money to invest.

GPL is anathma to Carl

an anathema

Yeah, I remember how Carl looked at GPL 5-6 years ago, but I've hoped 
that he might have changed his POV looking at how others do (and 
sometimes succeed).

I think that this dual licensing scheme works only when you reach 
a critical mass of users. Given the size of the REBOL community, 
he should just BSD everything and hope enough people would be attracted, 
and when the criticial mass is reached, monetize REBOL with paid 
services, custom builds, dual licensings, goodies (REBOL mug and 
vines),....whatever.

I've got a REBOL notepad ...anyone want to buy it?? :)

If it has a nice splash screen with a 3D rotating logo (all in REBOL), 
I might buy one. ;-)

It's paper!  Allen gave it me a few years ago when I was in that 
part of Australia ...

So, it's a collector!

I still have REBOL flah somewhere, as well as t-shirt :-)

Yep .. collectors item

Maybe we should do REBOL community reunion, even without RT, who 
knows when next devcon is going to happen. I would like to see you 
guys, before we close the shop here :-)

I thoght the next devcon that I was not going to attend was in Prague?

yes ... but it was ... cancelled ... or let's say ... postponed ....

I would be glad to visit Prague and see other rebolers.

Perphaps next spring - official launch of R3.1, View/OpenGL, Dual 
licensing, HTC, BlackBerry adopting R3, etc. - good stuff ahead :-)

29/1-01:03:23.766-## Error in [task-handler-1055] : Make object! 
[
    code: 303
    type: 'script
    id: 'expect-arg
    arg1: 'arg1
    arg2: 'attributes
    arg3: [block!]
    near: [arg1: err/arg1 
        arg2: err/arg2 
        arg3:
    ]
    where: 'html-form-error
] !

Now my site has all that binary stuff in front of it ...

It seems that error argument passing in 'html-form-error is not secured 
for unset! values. I'll patch that today.

Using latest SVN version?

no .. it's an encapped version

0.9.19 ?

Dunno .. the tray menu doesn't say

build date of august 2009

wow ... restarted Cheyenne and killed it again :(

time for some debugging

That would make it an early SVN version (around r5-r15).

Were there some critical enhancements I missed out on?

just sync and read changelog ... it is ... extensive :-)

Looking in my code, the unset! issue in html-form-error is already 
fixed in current version.

ok ... I guess I need to do another encap

Yes, there was a few critical fixes, and especially one for response 
buffer corruption. If you hit these bugs, I can only suggest you 
to upgrade.

Btw, I'm planning to freeze current SVN for a couple of weeks to 
release a new official version. I still have to patch a few recently 
added features and test the MTA more extensively first.

I'll setup a new CureCode instance for Cheyenne (and CureCode itself) 
this weekend. It would make it easier to follow Cheyenne's fixes.

I was reluctant to do that before, CureCode wasn't able to run multiple 
instances of itself on the same Cheyenne. Since 0.9.10, it's fixed, 
so I'm in the process of collecting all my current CC instances scattered 
around on multiple servers on the same Cheyenne server.

<and put them> on the same Cheyenne server.

Let us know when it's all working so we can do the same :)

It's already working now with latest Cheyenne+CC. I already have 
a Cheyenne instance running 2 CC instances for a customer since a 
week without issues. I've tested locally with up to 4 instances, 
each with different settings without any issue so far.