AltME groups: search

Paul, if you've got any questions, I've played around A LOT with 
the install instructions, since I now have a solutions with 3 projects 
and inter project dependencies...


its the first time I really use visual C, so it wasn't obvious to 
begin with, but I do understand most of it now.  it took me a few 
hours to get this new setup working with the host, the extensions, 
my OpenGL extension and the callback thing.

I've replaced all the paths by using the various $(...)  macros.

Ah, that would do it. The MinGW installer says it's going to set 
the path, but it fails at doing so. You have to do it yourself.

Peter: 

>> to binary! 10000.0
== #{40C3880000000000}

>> to binary! 10000
== #{0000000000002710}

Why do you think they should be the same?

then why do you think, that this is a bug?:

>> to decimal! to binary! 10000.0
== 10000.0

Not sure what specific data transformation Maxim needs.

I'd be interested in the REBOL code to do would would seem to be 
a simple transformation:
  How do I get from:

    #{0100}   ;; two bytes of binary, perhaps read from an external file
   to:

    256          ;; the equivalent integer (given the implicit endian 
    assumptions)

... and then we still wait for much needed improvements to Extension 
interface. It needs to support Devices definitely. No easy way to 
do callbacks right now, etc.

And I agree with Jerry, that it's quite urgent bug. It's hard to 
start writing some network schemes when you can simply test, that 
there is something wrong inside. If someone is able to "beep" Carl 
a little bit, please do it.

>> reduce [a: 2]
== [2] ; not what we want

>> reduce [to-set-word 'a 2] 
== [a: 2] ; what we want


Useful when building REBOL code or objects bit by bit. In R3 with 
extensible objects, you don't have to do that, though.

as follows: reduce [quote a: 1 + 1]

, i.e. in situations, where you actually do want to compute some 
parts of the block

Pavel, what happens for me is that:

1. I start the server and it waits like it should

2. Then I start the client and transfer begins. At some point around 
10-20 MB in, the server just stops and the client returns to console. 
After a few seconds the server also returns to the console.

3. If I then start the server again, the read continues for another 
80000 bytes, like this:

>> do %/c/serve.r
Script: "Untitled" Version: none Date: none
subport read
len: 32000 total: 19192000 of 406258740...read
subport read
len: 32000 total: 19224000 of 406258740...read
subport read
len: 9000 total: 19233000 of 406258740...read
subport read
len: 7000 total: 19240000 of 406258740...read
subport close


And then the port closes and the server quits again, unless I start 
the client.

especially the send-chunk function which seems to do some recursive 
stuffs

it's not adapted to have several clients
 <- but why do I get problems, then?

well, we still need to figure out what goes wrong. do you start the 
client or the server first?

We developed a TCP server program using R3-a96, trying to make it 
run in Linux as a daemon program (i.e. running in background), however, 
we failed. It just couldn't run in background.

We've tried the following 4 methods:

1) ./rebol my-server.r -s 8000
The process status is "T"

2) nohup ./rebol my-server.r -s 8000
The same as (1)

3) setsid ./rebol my-server.r -s 8000

This one worked, but it refused to return the session, which is not 
acceptable for us. If we do this in a shell script, anything after 
it won't be executed.

4) echo ./rebol.bin | at now

It shows "Can't open /var/run/atd.pid to signal atd. No atd running?" 
Our shell script didn't have the privilege.

Please help me. Thanks.

to-binary [1 1 1] should do #{010101} but doesn't work for me in 
A96, is it intended? Documentation tells should work.

well... it is daring to do anything with R3 at this point... :)

Via the host code, actually. We can't do device extensions yet, but 
we can ad device types to the host code.

Pekr, I don't know the whole target feature set aside from what's 
in the document. However, I do know that SSL and ODBC are nlikely 
to be added for the 3.0 beta release for significant practical reasons. 
The R2 release doesn't change that because R2 already had that code, 
and it's not at all portable to R3.

Coercion to decimal would be to prevetn overflow. I prefer not to 
do that though.

Rare for the kind of thing you tend to do though (emulators, iirc).

easy to talk hard to do

Or do you mean use a dialect to define the scheme?

switch type? %test.r [ .... ]

what do I need to write in the block to catch it ?

so return of 'type? is not a type? Well, we have not a datatype type? 
Yes, we have - datatype! .... but help reveals you can't do "to-datatype" 
...

The basic function to load REBOL code is DO. Most types are constructed, 
not literal. Even the scoping is procedural.

Needed to do reverse dns lookups

Also, for testing purposes... if you need to add a system/standard 
object, just unprotect and append to the object. I think the kernel 
will accept that. (But, do not reMAKE the standard object!)

You were supposed to do the rewamp, no? :-) Now as Graham produces 
schemes, we will be lazy to redo it :-)

What do you know about those countries btw? ;-) You were supposed 
to - was to BrianH ... I have some 10-15 sec lag here ...

Pekr, I was going to work on the network scheme revamp after that. 
I have to put things I already know how to do first, and there are 
a few LOAD and module changes that have accumulated that I know how 
to do already.

eh, I am out from net in something like 30 minutes. The four star 
hotel charges 15 EUR for 100 minutes of wifi. That is stupid :-) 
When we do wifi, we suggest hotels to provide such service for free.

though I do want to run Cheyenne on them !

I have one R3 question...is this bug or was it changed intentionaly 
in R3 (don't remember right now):

>> a: [[1 + 2]]
== [[1 + 2]]

this is OK:
>> do a/1
== 3

but this doesn't evaluate in R3:
>> do to-path [a 1]
== a/1

>>

I would say: intentionaly
>> do get to-path [a 1]

that is possible...I'd like to know the reason why it was changed 
as it is not symetric word! now...

in R2:
>> a: [[1 + 2]]
== [[1 + 2]]
>> b: [a a/1]
== [a a/1]
>> do first b
== [1 + 2]
>> do second b
== [1 + 2]
>> b: ['a 'a/1]
== ['a 'a/1]
>> do first b
== 'a
>> do second b
== 'a/1
>>


but in R3:

>> a: [[1 + 2]]
== [[1 + 2]]
>> b: [a a/1]
== [a a/1]
>> do first b
== [[1 + 2]]
>> do second b
== a/1
>> b: ['a 'a/1]
== ['a 'a/1]
>> do first b
== a
>> do second b
== 'a/1
>>


I think the R2 behaviour is more cleaner but maybe I'm missing something?

I don't have time to explore further at the moment. I'l try to do 
so later if nobody else has.

made the etag settings ... not helping so going to do a wireshark 
trace to see if I am setting it

then this has nothing to do with cheyenne, add something like
join %? checksum form now/precise ad the end of requested url

no .. I guess I'll have to do a wireshark trace to see why it doesn't 
work.

When stunnel starts it says "Wrote 1024 new random bytes to /root/.rnd" 
.. the certs are 2048 bit .. do you think this the problem could 
be that stunnel expects the 1024 byte cert/key ? (the sample cert/key 
taht worked was 1024 byte)

Currently there's only URL=>script aliasing available, but looking 
at the ALIAS code, I think that : 
	alias ".html" /cgi-bin/rebol-cgi-dispatch.cgi

might work (need to be tested). Do you really think that there's 
much users waiting for that feature?

Is this scheduler part of Cheyenne or Uniserve?  Just not sure what 
it has to do with Cheyenne

Is it to give those tasks hanging around something to do :)

Something I'd like to do is run a backup of my database, compress 
it and upload it to S3.  I use a script for that at the moment .. 
so maybe I can use the scheduler.

I do not need captchas, as I just want to couple some system.

If I want to do REST or SOAP, can I use Cheyenne?
Where do I have to intercept?

What technique does cheyenne use in regards to spawning of new processes? 
I mean - it either uses 'launch or some form of 'call. I wonder, 
what is the IPC (inter-process communication) strategy. E.g. I have 
10 requests I want to handle simultaneously, I spawn 10 processes. 
How do I pass TCP port to them? Or does it work some different way?

Do you use any specific dialect for IPC, or just some basic parsing 
methods? Those questions are just theoretical. Now I am more interested 
into how do I let Cheyenne use R3 for CGI process, instead of R2, 
just to do some testing?

To support R3, you have to either hack CGI.r source code to force 
REBOL script to use the general strategy (simple to do, but probably 
poor performances) or implement a mod-R3 extension to setup a custom 
R3 persistent server (more work but faster result).

How is that? Under Apache, I do have to have both - shebang line 
plus REBOL header .... Yes, I understand why the precedence was set 
- because of fast-cgi mode precedence ...

Or ... better yet, use NAT to reroute port 80 to something above 
1024 and run Cheyenne from user space listening on the non-priv'ed 
port??  Safer (I think) if anyone ever assumes control of your server 
internals.  Or do you need root powers for something other than listening 
on port 80?

Best way to redirect domain.com to www.domain.com: correctly setup 
the DNS records.
Best way to do it in Cheyenne: (untested)

domain.com [
	root-dir %/...
	redirect 301 "/*" "http://www.domain.com"
]

www.domain.com [
	root-dir ...
]

Btw, in order to forge emails to be sent, I've tried to rely on REBOL's 
builtin email support functions (big mistake!). You should know that 
they *are not* RFC compliant, the biggest issues being :


- emails produces by REBOL are using LF as EOL instead of CRLF (RFC 
2822). See http://cr.yp.to/docs/smtplf.html

- headers are not encoded for non ASCII-7bits characters (RFC 2047)


So, I've deeply patched the builtin code at runtime to workaround 
this, but, I should have better rewrote it all from scratch (that's 
what I intend to do when I'll have enough free time).

I think I found a different way to do this with symlinks. Thanks.

Two other issues in the 0.9.19 source:


1. INCLUDE and INCLUDE-FILE do not process paths identically. This 
is not mentioned in the docs.

2. INCLUDE won't include files in absolute paths. It simply changes 
the path to the current path which stores the RSP file that is currently 
being executed. I can't say that I have a fixed include directory 
somewhere at an absolute path. I don't see the purpose of altering 
the path like this.

My app reports errors back to me ... 

I do a set-net [ [myemail-:-gmail-:-com] gmail-smtp-in.l.google.com ]

and then send the message to me.

Couldn't access my Win7 box, so could test it. I'll be able to do 
that only tomorrow.

ok.  I'll fire up wireshark.  But my users won't be able to do that.

no matter ... I found a way to do this via content-type  ...


just need to translate this php to rsp http://www.dklevine.com/general/software/tc1000/jarnsample3.php

Re: greylisting, the plan was to use the freshly integrated scheduler 
library : scheduler/add [in 5 mn do [resend <email-id>]]

Thanks Graham - what should I do with the first run of Tortoise? 
I suppose I better don't do Check-out? Should I create a "working 
copy"? I don't remember how I did it for Rebgui, as I am long time 
issuing Update item from the context menu. I need to do first sync 
of Cheyenne now, and would not like to screw something on the server 
side :-)

you want to do a SVN update

I'm need to get the name I assigned a face when I alt-click on it. 
I can get its style, offset, size etc but I do not see a way to get 
the face's name. More specificly I have multiple scroll-panels and 
I need to know the one I'm clicking in...

I like the fact that I can pass a file! so that I don't have to figure 
out how to do a multipart upload to the mail.rsp script.

I'm just trying to do a file upload using RSP ... see http://rebol.wik.is/Cheyenne/Upload-file.rsp

I'm about to build a user login system, but I would like to know 
if it's a good idea to make this a public project so others can follow 
and contribute? Would it be a good idea to include it in Cheyenne? 
I don't intend to use MySQL for it as the rest of my site isn't DB 
driven.


I've not done anything yet, so I also need to know, what Cheyenne 
can already do in this area, to avoid duplicating functionality. 
Can I completely rely on the session context, or are there crucial 
parts missing?

Doc, thanks.

What I need to do is basically the whole package:

Sessions, which Cheyenne can do.
Login process with authentication. AUTH config, perhaps.
Log out process, also possible.
User adding and removal process. This needs to be added.
Privilege usage and management. Also added separately.

I'll have a closer look at the built-in AUTH config keyword.

Let me know if it's an urgent need for you, I might do a quick change 
in the next revision to give you a workaround.

doc, no I didn't as that would start up a new App process which seems 
excessive to just do a download ... especially when Cheyenne is already 
running in the background :)

just thought I'd drop a little note that serious remark module work 
has begun.  I was trying some stuff before, but starting too wide 
and I wasn't able to get traction on the project.  now I'm just integrating 
the v2 remark parser into a mod.  


One cool thing that it will do out of the box, is handle statically 
parsed files. basically, you build .html files using remark dynamic 
tags, they are saved out in a cache dir and then the url-file function 
will redirect to the parsed file, if done, or will run the parser 
on it and then cache it.

sure... I've impleted some purpose built multi-threaded servers in 
python and its quite easy to do.  probably the last real limitation 
in REBOL right now.

ok... with this info I've done a few tests and I see the config files 
allows you to dump pretty much any thing anywhere... is the  'in 
keyword only for the 'do to be recognized within one of the setup 
blocks?

Pekr: it would not work that way, the CGI handler in worker process 
will try to DO the file.

well... the main call to remark is ... compile   hehehe...  I do 
plan on making an XML document model eventually.  basically, it would 
convert XML elements into your current Remark document models, so 
you can leverage the same code base but with another data model as 
input.


optionally you could build direct XML document models for a bit more 
speed.


all that needs to be done to make it easy for you guys is to build 
a few simple base XML tags which allow you to build the dialect based 
on xml element names.

Doc, I have a question, and possibly a suggestion based on the answer:


is there a way to tell cheyenne  to HALT when it finds ANY config 
error?


I have been having a lot of problems that where due to the config 
not being ok and me not seeing the (shy) error message... 

currently, cheyenne starts and its in an invalid state ultimately 
doomed to failure and without a clear way to determine what's going 
on when the requests do strange stuff.

Getting an error trying to get php running with cheyenne.


Works fine on xp pro but on mt win server 2003 box I get a dialog 
saying "apppication is configed incorrectly. Reinstall may fix..."

(I get this when I try to run php from the php icon. In xp pro I 
would get the dos box indicating that is was running) 


I know its nothing to do with cheyenne but has anyone seen this...
php is not installed

but I don't want to nag you too much , because again I am not sure 
if I shouldn't try to do this on nginx side for this specific website

alias "/path/to/target" %script  -- I found this  .. can I use regex 
or something else to do 

AliasMatch ^/some-(.*) /script.rsp?a=$1

Erratum: request/headers/location has nothing to do with aliases.

what do you mean with has nothing to do?

There's nothing specific you have to do on the web server side except 
providing the service interfaces (regular HTTP responses)

My example is only fourty lines or so and implements a complete command 
service bus; similar to REBOL/Services but much simpler, so JavaScript 
can do it

I'd say one Uniserve handler should normally be able to handle several 
tens of requests per second, so even when you would let each client 
browser do a poll request every second, compared to that you loose 
at least an order of magnitude in scalability with Comet

Doc - just curious - how do you know, which worker process is free 
to work? :-)

set-cookie docs don't exist and it says n/a .. does this mean the 
word is not there any more or something else? Do I have to manually 
set http response headers to set cookies?

I used to run several Cheyenne instance on linux server but it was 
a long time ago (v0.9.15 or 16). I didn't do much testing on that 
use case since then.

Janko, I have many app-init.r and do not see any problem, if you 
sand me your app-init from both virtual host and tell me exacltly 
what is the problem you are seeing, I'll be glad to check that

Janko, about the app-init code you've uploaded, just a side note 
: you're loading a *lot* of code (libs?) on each RSP request, this 
is surely slowing down each request a lot. You should be loading 
all these libs in 'on-application-start instead. (btw, "simpauth.r" 
is loaded twice)


About local testing, you can use virtual hosts locally too in Windows 
easily. Just add them to C:\Windows\System32\drivers\etc\hosts file. 
Add them all after 127.0.0.1 (but do not use exactly the same domain 
name as the remote ones or you won't be able to access them anymore). 
I use shortcuts of my real domains for locals : softinnov.org => 
si.org, curecode.org => cc.org, etc...

@Doc: 

- I am not totally sure I correctly understand what you mean about 
webapp. I will need to process and try it some more.

- About code loading on on-page-start : yes I know of that, I am 
using it as dev setup so I know latest code is reloaded each pageload. 
I intend to set it on     on-application start when fully in production 
(But I have to admit the server is bgehaving really fast even with 
this setup all along)
- good catch, I will remove one simpauth.r

- I am aware of hosts file, but so far decided to edit the cfg file 
each time I switch ... which is in retrospect getting a little tiresome 
with more and more apps so I should think of  some naming convention 
for getting to all domains local and do it that way yes

- great for multi instance support . I also already ported site-assistant 
to 0919. it was much less work than I thought.. mostly just few things 
like do -> do/global and some 3 other tricks (no really aplication 
level changes were needed)

SVN: Can someone give me a short note how to best get the SVN version 
into a "production environment"? Is it one file I can just run on 
the server? Or do I need to build it myself somehow?

I can envision a day when everything will have an "always on" connection 
with everything else that is important.. probably via websockets. 
 ie: my email, chats, voicemails pushed to me wherever i am, and 
on whatever device. The ability to do this is nothing new (SOAP, 
XML-RPC etc), but what is missing is a homogenous catalyst... the 
webserver seems the most likely candidate, as they are the de-facto 
interface to the world's DBs. This is my vision for Cheyenne, that 
of an Uber-server.

It opens up the possibility to do similar things, yes, while still 
being able to fool firewalls

Needs to be in a forever loop somewhere. I'm guessing a service (or 
protocol.. can't remember which)
so that you can connect and to this.. 

forever [

do %somehandler.r

]

where somehandler.r could manage the connections? no?

<snip>

EOM: "\n"
; prints messages to console.
verbose: false
; opens port
io-port: open/no-wait tcp://:7001
clients: []
; numbers of clients
nc: 0
; max clients limit
mc: 50

..... 

forever [


;Events are periodical functions.. checking if a website is still 
up etc. Add a wait state to prevent excessive CPU usage
;wait .02 
;if not empty? %events.txt [do load %events.txt]

either none? (wait [ .01 io-port])
            [ clients: head clients ] [
		
            print "a user is connecting"
            either ( nc < mc ) [
            append clients make object! [
                        port: first io-port
                            ]
            nc: nc + 1
            respond rejoin ["Connected to ROCKSTaR" EOM ]

... 

etc

I'm on port 80 ...


I see the button and get the hello world message popup as well as 
a "comm opened" popup at start...


I was trying to get Terry's demo to work but his "Drag this" does 
not seem to do anything...

Anyone try out Terry's?

Also could not get  ws.rsp to work..."page cannot be displayed"

This is what I'm looking to do.

- A client connects via websocket.

- Client sends message "a". The server runs the following

forever[
n: read http://cheyenne-server.org/blog.rsp
prin n
wait 1
]
 
- Client sends second message "b". The server runs the following

forever[
x: read http://rebol.com/cgi-bin/blog.r
prin n
wait 2
]

These loops should be non-blocking.

I think that many ppl here think that the priority of importance 
is:

- host release
- host support of View (merge of DELECT and command type)
- Extensions supporting Devices, callbacks
- tasking, IPC
then beta ....


If you postpone anything from above to 3.1, some ppl will wait for 
3.1 ... do you want to bet with me? :-)

So, if no devices have "work to do" then we sleep for a short period 
of time (as long as that period is greater than the minimum dispatch 
time for the host CPU.)

Intranet voting in RSP: "simple things should be simple to do." ;-)

Henrik - yes, just read the discussion. Carl claimed, that RT has 
long time the code to IPC between processes. I objected, that no 
such code was standardised over-time, so that is maybe a reason, 
why ppl do wait for tasks. We await stuff like ipc:// scheme, etc.