World: r3wp

Hrm...  The script wasn't loading the image where I thought it was. 
The data was actually Binary!  not Image!  so I'll have to do some 
more digging...

I saw such issue in Cheyenne a few times with an older REBOL version 
(2.5.xx) and it was caused by a REBOL GC bug. Never saw such behaviour 
since then.

I'm using the encapped version...

Heh...  A more effecient design goes a long way.  I've minimized 
requests to the server and dropped the memory usage by about 75%


Speaking of minimized requests...  Has anyone done any AJAX/JSON 
stuff with Cheyenne?

Yes

Can you elaborate or point me to something somewhere that demonstrates 
how you did it?  I'm being lazy and I don't want to figure it out 
on my own. ;-)

Ask Terry ... he has he says.

I also installed the yahoo javascript libraries ... and they're using 
Ajax ... and it's all being served by cheyenne

Ajax is just javascript making an asyn http call

I know what AJAX is.  ;-)  I've used it many times, I've just never 
set up the server side before.  I am planning on using the json.r 
script from the Library...  I'll just play with it and see what I 
come up with...

Strange...  


I added some working JSON...  Somehow the .rsp file handling the 
JSON request is using functions that aren't including in the rsp 
file.  Is it supposed to do that?

Do you have an example?

I have tag.r that has 

tag: context [add: does [something]]


I DO tag.r on most of my RSP pages but not on json.rsp yet I'm using 
TAG/ADD in json.rsp without problems.

Sounds like it is being set globally?

tag is being set globally but I didn't expect includes to be persistent 
across different pages.

Having your TAG word already defined is a side-effect of persistent 
RSP processes. You should *NEVER* rely on it, because your script 
can be executed within a different process where the word may not 
have been defined.

Btw, if your %tag.r script is required in most of your RSP scripts, 
just DO it once in 'on-session-start (in %app-init.r).

btw, love the new website  :-)

feature request: add on-global-page-start and on-global-page-end, 
same as on-page-start and on-page-end but executed for all rsp pages, 
not only for webapps

Maxim: thanks, it still needs a lot of work to be completed : integration 
of a CureCode instance for bug tracking, writing lot of documentations,...

Will: I'll consider that for the next release.

Has anyone written Atom or RSS output code in RSP? I am going to 
need to do so right away and every possible speedup helps.

I remember an RSS output snippet. It's probably in the REBOL library

By Chris, if I'm not mistaken

http://www.rebol.org/view-script.r?script=emit-rss.r

http://www.ross-gill.com/page/Atom+in+a+Hurry

Thank you both :)

Graham, did you ever get to switch to slicehost or linode?

I have slicehost. Highly recommended.

Fast, super simple. Not the cheapest, but you definetely get what 
you pay for (which is very good, in their case). They also have good 
docs and wikis - that's an example for many services!

What's the minimum you need to run Cheyenne?  the encapped binary 
and what else?

A config file, but if you don't provide one, Cheyenne will create 
a default one in the same folder.

Thanks

This is interesting.   I'm launching cheyenne on startup each time 
my app starts.  But to see if it is already running, I check by opening 
a port.
p: open/direct tcp://127.0.0.1:8002 close p


but this causes Cheyenne ( latest encapped version ) to shut down!

I tested this with the above and a rebol console to reproduce it.

I guess I should check with read http://127.0.0.1:8002 instead, but 
that's slower.

but does it mean I can crash any Cheyenne server remotely at will?

Graham, try mine and let's see what happens.

although I still am running an older version...

I have to go for a bit...

Oops .. changed this group to non web public ...shouldn't have posted 
this is a web public group

No, it's okay with yours.  I'm guessing it only crashes on localhost.

phew!

Graham, do you have any custom services? no problem here with that 
code:
  p: open/direct tcp://127.0.0.1:80 close p  
  p: open/direct tcp://127.0.0.1:80 close p
  p: open/direct tcp://127.0.0.1:80 close p
  p: open/direct tcp://127.0.0.1:80 close p
  p: open/direct tcp://127.0.0.1:80 close p
  read http://127.0.0.1:80                        
;   {<html>
<head>
^-<title>Welcome!</title>
</head>
<body>
<img src="logo.png">
<center>
<h2>Congratulations, you are running Cheye...

this is just the Cheyenne binary ... nothing else, and running on 
8002

hmmm, I'm running from source

>> p: open/direct tcp://localhost:8002 close p p: open/direct tcp://localhost:8002 
print "ok"
close p
** Access Error: Cannot connect to localhost
** Near: p: open/direct tcp://localhost:8002 print "ok"
>>

the ok does not print because Cheyenne has quit

this though is fine


>> p: open/direct tcp://localhost:8002 print "ok" close p p: open/direct 
tcp://localhost:8002
print "ok" close p
ok
ok

so timing appears critical

Graham, I have to check my console, because I think mine auto-restarts 
on quit.