World: r3wp

Since many of the 2.7.8 native fixes were done for Doc, perhaps he 
will do new encaps.

I haven't used 2.7.7 due to a few issues that made it look less stable 
than 2.7.6. I can't afford to use a new version with regressions. 
Hopefully, SDK 2.7.8 looks more polished and it runs Cheyenne flawlessly 
on Linux platform. If the Windows SDK is ok too, I'll upgrade my 
Cheyenne build chain to 2.7.8.

MikeL: 

- Download Cheyenne revision 122 source package from here: http://cheyenne-server.org/download.shtml
- Open a 2.7.8 console
- Type: 
>> cd %<path-to-cheyenne-folder>
>> do %cheyenne.r

Thanks I had tried that combination a little earlier and after running 
in Windows Auth mode, I get  "Can not open server Rconsole on port 
9801" and "Can not open server Logger on port 9802" as Uniserve errors.

and are those ports already open?

Does Rebol need to be run as admin?  Is your firewall blocking these 
ports?

Thanks Graham.   For some corporate machine, changing the firewall 
settings won't be an option.  I ran R2 as admin and gave R2 access 
to everything.  No change.  9801 and 9802 are not recorded as blocked 
for any programs on McAfee inbound or outbound events.

Cheyenne is working fine from sources with 2.7.8 (XP)... Check what 
is using the port.

You can use for example PortQry util: http://support.microsoft.com/kb/832919
Which can show you something like that: 
...
Process ID: 1376 (rebol-view-278-3-1.exe)

Process doesn't appear to be a service

PID	Port		Local IP	State		 Remote IP:Port
1376	TCP 8080  	0.0.0.0 	LISTENING	 0.0.0.0:22712
1376	TCP 9799  	0.0.0.0 	LISTENING	 0.0.0.0:41163
1376	TCP 9801  	0.0.0.0 	LISTENING	 0.0.0.0:43253
1376	TCP 9802  	0.0.0.0 	LISTENING	 0.0.0.0:22573
1376	TCP 9803  	0.0.0.0 	LISTENING	 0.0.0.0:40994
1376	TCP 9799  	127.0.0.1 	ESTABLISHED	 127.0.0.1:1116
1376	TCP 9799  	127.0.0.1 	ESTABLISHED	 127.0.0.1:1117
1376	TCP 9799  	127.0.0.1 	ESTABLISHED	 127.0.0.1:1118
1376	TCP 9799  	127.0.0.1 	ESTABLISHED	 127.0.0.1:1119

This tools is maybe better http://technet.microsoft.com/en-us/sysinternals/bb897437
as it has gui as well

You don't need any special tool for port checking in winXP...just 
use the console NETSTAT command.

Thanks. I am run Windows 7 and ran NetStat as Admin.  Some 9799 and 
other ports in use but no 9801 and 9802.  Trying  TcpView.

Netstat does not display which process is using the port, does it?

Oldes, use netstat /? to get all the options...I guess -o is what 
you need.

I don't need it:) btw... it's -b

Thanks for the help.  R2 is listening on 9801 and 9802 now.   Next 
step is to get it to server a page.

Since many of the 2.7.8 native fixes were done for Doc...

 Brian, where can I see this list of fixes? I guess on RAMBO, but 
 it's down since yesterday...

It says you collaborated with Carl :)

I don't know what he did to make Cheyenne better, except ACCESS-OS. 
There were other native fixes to Linux builds mentioned, but I can't 
test on anything other than XP at the moment so I didn't ask for 
a full list. Given the "coordinated with DocKimbel" comment I figured 
you knew better, but that might just be the ACCESS-OS thing, which 
currently does nothing on Windows, and doesn't require an SDK. We'll 
know when the changes doc is updated.

The fixes that I expect would be Library Component included in Core, 
and View being able to start without X11 running

I wouldn't expect the latter, as most of what makes View different 
from Core depends on X11. Some image support might be possible in 
Core though. Agreed on the former: If /Library is free, /Pro should 
be free too.

It was in the planning since a year

Well, if Carl says it's possible then it is.

I collaborated with Carl on ACCESS-OS only.

What does that do?

Allowing calls to getuid/setuid/getpid/kill.

The goal was to be able to run Cheyenne with /Core on Linux without 
the need for /Library/

OK. Do you have ideas for stuff it might do on Windows?

Sigh... why not just include Library?

/Library: I don't know.

Windows: nothing more than you.

Some weird business customer consideration, I would guess. But then 
Library shouldn't have been promised for 2.7.7

I was also a bit surprize by the inclusion of those OS natives instead 
of just freeing /Library on Linux, but I guess it's business related.

I'm also surprised by the bad design. ACCESS-OS is extremly ugly. 
To kill a process:

access-os/set 'pid 29110

Library wasn't in Core at all. It was in View, so that was just a 
matter of tweaking the licensing code. For Core it would mean either 
adding the licensing and library code, or just renaming Pro as Core. 
View did get Library in 2.7.7. It's not just a business thing, it's 
also a matter of time and effort.

About the possible "fixes" that Cheyenne could benefit from, Carl 
added the helper task (for async DNS) deferred boot to workaround 
setuid issues (security improvement when running Cheyenne as not 
root user).

Cool, those sound useful.

There's nothing complex about keeping promises

Andreas: I share your feeling. I guess that it's easier and safer 
to add a new native in R2 than integrate all that stuff into system:// 
port (using set-modes/get-modes as interfaces).

I am in favor of releasing Pro as Core and just disabling the licensing 
code; that would give us Library on Core a lot quicker than trying 
to retrofit things into Core. R2 is quite an old codebase, so a lot 
of changes would require a huge amount of work - R3 was rewritten 
for good reasons.

Probably time to move this discussion to !REBOL2 Releases.

I can't get cheyenne to serve to an ajax json request.


I can get it to read the array as a local file but it does not seem 
to work through url request.


I played with content-type: application/json which I read was needed 
but I don't know if I'm on the right track.

For example: 
json data: 
{
  "foo": "The quick brown fox jumps over the lazy dog.",
  "bar": "ABCDEFG",
  "baz": [52, 97]
}

and the js script to fetch the data:

<script>$.getJSON('http://localhost.jsontest.cgi', function(data) 
{
      alert("JSON Data: " + data.foo);
});</script>

It works fine for me
I have in my RSP pages

Print json-data

This doesn't look like a valid URL: 'http://localhost.jsontest.cgi'

should be http://localhost/jsontest.cgino ?

yes...i just typed it here wrong....thanks

my local script: 
<!DOCTYPE html>
<html>
<head>
  <style>img{ height: 100px; float: left; }</style>
  <script src="http://code.jquery.com/jquery-latest.js"></script>
</head>
<body>
	

<script>$.getJSON("http://localhost/jsontest.cgi”, function(data) 
{
      alert("JSON Data: " + data.foo);
});</script>
</body>
</html>

my rebol cgi script:
#!/cgi-bin/rebol.exe -cs %s %s
REBOL [Title: "json test"]
Print {
<html>
<head>
<title></title>

<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">

</head>
<body>
{
  "foo": "The quick brown fox jumps over the lazy dog.",
  "bar": "ABCDEFG",
  "baz": [52, 97]
}
</body>
</html>
}

Alan, I'm logged in to AltME from Ubuntu - so many non-ascii characters 
get displayed incorrectly. In your script the closing double-quote 
after /jsontest.cgi doesn't display properly. Perhaps you could check 
that it really is a double-quote and not a "smart-quote" in the actual 
source.

Amacleod: Your CGI script headers looks very wrong:
- What are those "%s" on the shebang line?

- /cgi-bin/rebol.exe: this doesn't look like a valid filesystem path

- Why the Content-Type header isn't emitted as required by CGI specification?


Maybe you should read again documentation about REBOL CGI usage on 
rebol.com site and also have a look at CGI sample scripts provided 
with Cheyenne source package. Understanding what a shebang line is 
might also help: http://en.wikipedia.org/wiki/Shebang_(Unix)

When i go to the cgi script directly in the browser I get my json 
data displayed. the cgi seems to be working.