r3wp [groups: 83 posts: 189283]
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r3wp

[!Cheyenne] Discussions about the Cheyenne Web Server

Terry
28-Jan-2010
[7761x3]
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/
james_nak
29-Jan-2010
[7764]
Doc, is there a binary for the latest Cheyenne that works with curecode?
Dockimbel
29-Jan-2010
[7765x2]
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.
Graham
29-Jan-2010
[7767x2]
GPL is anathma to Carl
an anathema
Dockimbel
29-Jan-2010
[7769x2]
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.
Graham
29-Jan-2010
[7771]
I've got a REBOL notepad ...anyone want to buy it?? :)
Dockimbel
29-Jan-2010
[7772]
If it has a nice splash screen with a 3D rotating logo (all in REBOL), 
I might buy one. ;-)
Graham
29-Jan-2010
[7773]
It's paper!  Allen gave it me a few years ago when I was in that 
part of Australia ...
Dockimbel
29-Jan-2010
[7774]
So, it's a collector!
Pekr
29-Jan-2010
[7775]
I still have REBOL flah somewhere, as well as t-shirt :-)
Graham
29-Jan-2010
[7776]
Yep .. collectors item
Pekr
29-Jan-2010
[7777]
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 :-)
Graham
29-Jan-2010
[7778]
I thoght the next devcon that I was not going to attend was in Prague?
Pekr
29-Jan-2010
[7779]
yes ... but it was ... cancelled ... or let's say ... postponed ....
Dockimbel
29-Jan-2010
[7780]
I would be glad to visit Prague and see other rebolers.
Pekr
29-Jan-2010
[7781]
Perphaps next spring - official launch of R3.1, View/OpenGL, Dual 
licensing, HTC, BlackBerry adopting R3, etc. - good stuff ahead :-)
Graham
29-Jan-2010
[7782x2]
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 ...
Dockimbel
29-Jan-2010
[7784x2]
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?
Graham
29-Jan-2010
[7786]
no .. it's an encapped version
Dockimbel
29-Jan-2010
[7787]
0.9.19 ?
Graham
29-Jan-2010
[7788x4]
Dunno .. the tray menu doesn't say
build date of august 2009
wow ... restarted Cheyenne and killed it again :(
time for some debugging
Dockimbel
29-Jan-2010
[7792]
That would make it an early SVN version (around r5-r15).
Graham
29-Jan-2010
[7793]
Were there some critical enhancements I missed out on?
Pekr
29-Jan-2010
[7794]
just sync and read changelog ... it is ... extensive :-)
Dockimbel
29-Jan-2010
[7795]
Looking in my code, the unset! issue in html-form-error is already 
fixed in current version.
Graham
29-Jan-2010
[7796]
ok ... I guess I need to do another encap
Dockimbel
29-Jan-2010
[7797x5]
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.
Graham
29-Jan-2010
[7802]
Let us know when it's all working so we can do the same :)
Dockimbel
29-Jan-2010
[7803]
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.
james_nak
29-Jan-2010
[7804]
Sorry, Doc, had to sleep. I'm using Windows (XP).
Terry
29-Jan-2010
[7805x2]
I have an idea, if R3 is 'all the news', why not source R2?
I'll bet dollars to doughnuts R2 takes off, and R3 languishes.
Henrik
29-Jan-2010
[7807]
doubtful
Terry
29-Jan-2010
[7808]
put up your doughnuts
Henrik
29-Jan-2010
[7809]
open sourcing something doesn't magically increase its development 
momentum. been there, done that.
Dockimbel
29-Jan-2010
[7810]
It seems to me that there's a bit of misunderstanding here on how 
OSS works. My understanding is that peoples are willing to contribute, 
because they *need* something and they *can* obtain it by modifying 
the source code. Expecting that your product development forces will 
magically increase because you're going open source is, in the general 
case, an illusion. People will contribute only if they're interested 
in your product, have a need to fullfill, and time/skills to make 
it. So, a critical mass of users is required to get enough contributions. 
If you don't get enough contributions, don't blame it on the open 
source approach, blame it on your product (or on your communication), 
because it doesn't attrack enough people to reach the required critical 
mass.