AltME groups: search

Q: I have yet to see anyone here "overstaying their welcome". 

A: Let us focus on signal to noise, which seems to be the focus of 
Gregg's post.


Q:  And if no one is doing that, then why make the point?  Could 
it be a personal issue perhaps?  An "I'd rather not try to filter 
out stuff im not interested in, so stifle it." ?


A: Do you feel you have an axe to grind?  Is there something your 
reading into the cordial request to all to "please remember to stay 
on topic in groups." ?


I must have missed something, how did you jump from the sentence 
above, and the sentence "If you don't want to be bothered with a 
particular group, feel free to remove yourself from it. "  which 
seams educational (people do forget they can change the channel in 
censorship terms to "So if I'm "not welcomed""?


Reading your posts here leads me to believe you have taken what was 
written as if it was written to and for you, yet it seems to be written 
as general web etiquette but as it applies to Rebol3.

In CZ, we have NIC - central registrant, which does not accept any 
registrations and is only coordinator and State has its xy % of value 
there. We have to choose between various certified registrant companies. 
I did choose globe.cz and they are fine. They do care, they pay to 
NIC.cz and then they request money from me. Before the domain expires, 
I am notified, if I have nothing agains payment of next period and 
if there is any info I want to change ...

they seemed somewhat reluctant to respond to my request to transfer 
to registrar while it was active

So - if most ppl agree, that starting desktop and trying to connect 
to internet directly is good thing (with auto proxy detection it 
could be, without it it simply is not), then I want -i and --noinstall 
to skip Desktop launch phase - and that is what I am about to submit 
as a request, or as a bug report ...

Gabriele - isn't 'request-date somewhat unfinished?Try 'help request-date 
and look how is /offset described, what it says it accepts (any type) 
and what it really allows to accept (pair) ... Maybe this could be 
improved ...

i guess all request-* require some refinement.

besides that I wonder, if e.g. request-date as an example, works 
with locale element? I think not ... REBOL locale support is really 
terrible - nonexistant, and I wonder why, if system/locale/months 
is available ...

yesterday I got request of my friend Bobik here, asking how to localise 
it  :-) I suggested him to look into RebGUI calendar instead ...

ah, now I tested it, RebGUI works with system locale - besides that, 
the week starts by monday ;-) btw - could RebGUI code be reused in 
official rebol distro? e.g. as far as request-date is concerned, 
or even request-dir, it is of a much more quality than rebol's built-in 
ones  ....

I had done some enhancements to request-date in the days of "View 
1.3" project (2 years ago).

The result is in RAMBO, but not the code http://www.rebol.net/cgi-bin/rambo.r?id=3058&
So you can find it here with some demo code :
do http://membres.lycos.fr/didec/rebol/request-date-enhanced.r

RFC 2616
10.3.8 307 Temporary Redirect


   The requested resource resides temporarily under a different URI.

   Since the redirection MAY be altered on occasion, the client SHOULD

   continue to use the Request-URI for future requests.  This response

   is only cacheable if indicated by a Cache-Control or Expires header
   field.

   The temporary URI SHOULD be given by the Location field in the

   response. Unless the request method was HEAD, the entity of the

   response SHOULD contain a short hypertext note with a hyperlink to
   the new URI(s) , since many pre-HTTP/1.1 user agents do not

   understand the 307 status. Therefore, the note SHOULD contain the

   information necessary for a user to repeat the original request on
   the new URI.


   If the 307 status code is received in response to a request other

   than GET or HEAD, the user agent MUST NOT automatically redirect 
   the

   request unless it can be confirmed by the user, since this might
   change the conditions under which the request was issued.

Hi, i just posted a new bug on rambo: When calling 'request-file 
and clicking on Cancel, the value returned is %none instead of none 
--> makes more complicated to test the returned value. I tested under 
Windows XP

>> type? request-file
== none!

I've just found 'request-download function and it seems to me it's 
buggy. Can anybody confirm this?

>> request-download http://rebol.com
connecting to: rebol.com
** Script Error: Cannot use insert on this type port
** Where: read-thru
** Near: write/binary file data
if all

request-download - where did you find it ?

I was looking for some request function and found this one. There 
are more non-functional functions in REBOL AFAIK.

>> link-relative-path %./
** Script Error: link-root has no value
** Where: link-relative-path
** Near: either f: find/match file link-root

The request-download bug above I think is caused because file is 
actually a directory. So, the port type is 'directory and so the 
insert fails.

request-download usually works fine, you just need to provide a file. 
it downloads to the cache by default.

Anton: I know about your batch download, I was just looking for some 
other request function

The request-download bug is a bug in read-thru. Fix the bug in read-thru 
and you fix the bug in request-download.

ladislav, I understand that in the current version there is no native 
way to find the first value of integer! (not an integer! type value 
but the datatype value itself)  maybe that could be added to 2.7 
as a refinement.  its a valid request, especially since we are considering 
and openly commiting to updating the switch .   no?

It is still my greatest request though, that =anyword and \anyword 
/anyword be a part of the make-doc standard.  Thereby building MD 
dialects based on usage context.

When a new request is sent through a timeout-ed connection, my driver 
will close the port and try to reconnect to the server. It tries 
3 time and if it fails, generates an error.

Another question: what is required to use view-request.r with enface? 
I keep getting an error message:

** Script Error: sky has no value
** Where: context
** Near: color: sky size: 2x2
** Press enter to quit...


I just want a calander to pop up to request a date.  Is another source 
module required besides view-request.r?

Volker, that helps some.  But now I get:

Unknown word or style: request-date

I think I have included all the files needed. The problem must be 
in the way I am using request-date. Oh well, I figure it out after 
lunch.

sqlab, your answers (in order, and to the best of my knowledge):
- No.

- REBOL_Initialize, REBOL_Status, REBOL_WndProc. There isn't any 
current documentation as to the argument and return types of these 
functions. Some example code would be nice.

- Not to my knowledge, although the question of how to use this dll 
has been asked often. The Plugin group here was formed to request 
that the community create code that uses rebol.dll, and occasionally 
that request is repeated by the person that created the group, but 
progress stalled when people had difficulty calling the dll because 
of lack of documentation.

I think it's request-download makes reference to a user-prefs object 
which should be included in the main view sources.

Is there a better way to do this:

comment {
    ;do %/c/sdk/source/view.r
    do %/c/sdk-2-6-2/source/view.r
    do %t-db-functions.r
    do %request-date.r
}

    #include %/c/sdk/source/view.r ;NOTE: THIS IS THE OLD SDK. WON'T 
    WORK WITH NEW SDK.
    #include %t-db-functions.r
    #include %request-date.r


So that I don't have to comment out  lines when I switch from interpreter 
to encap and back.

Yes about usability. It's a all-in-one widget: one can use it to 
replace menu, lists, simple requesters (like the fonts and colors 
selection in MSWord), toolbars, auto-complete fields, etc. So it's 
mostly a shortcut to put more widgets (or compact them) in a window 
and can be confusing for users: what will happen if I select something, 
write in the field, click outside the list, click inside on the left, 
on the right, hit enter? It's a full requester in one widget: you 
can do the same with a request-list -like requester with ok/cancel 
buttons.

Latest build available at: http://www.dobeash.com/files/RebGUI-023.zip

Highlights include:

	- Changed default font from "Arial" to "Verdana"
	- Added label and table widgets
	- Added window-level 'do block support

 - Added 'reverse keyword to support windows style right-to-left widget 
 placement
	- Renamed set-title to show-title
	- Merged %request-file.r into %requestors.r
	- Renamed %gui.r to %rebgui.r and prefixed other files with same

Read more about these changes here:

	http://www.dobeash.com/it/rebgui/display.html#section-2.2
	http://www.dobeash.com/it/rebgui/display.html#section-3.3.2
	http://www.dobeash.com/it/rebgui/display.html#section-3.4
	http://www.dobeash.com/it/rebgui/display.html#section-4.3
	http://www.dobeash.com/it/rebgui/display.html#section-5.15
	http://www.dobeash.com/it/rebgui/display.html#section-5.26

request-color

** Script Error: in expected object argument of type: object port
** Where: wake-event

** Near: if in pop-face/feel 'pop-detect [event: pop-face/feel/pop-detect 
pop-face event]
>>

Here's another issue:
rebgui 0.2.4 defines a new global word 'edit

  This interfered with my custom edit function, which I use to launch 
  my favourite editor.
  I'm not changing it for you ! :)

  This is an example of the problem of adding words to the global context 
  without doing
  an environmental impact study first.

  The user should be given the choice whether to export your words 
  to the global context or not.
  But probably most of them don't need to be out there at all.

  My advice is to add only these words to the global context: [

 ctx-rebgui display show-text show-data show-title splash request-color 
 request-date request-file
  ]
  
  --- rebgui.r ---
  
	CTX-REBGUI: context [

		...

		edit: none
		widgets: none
		requestors: none
		display: none

		foreach [word file][
			edit		%rebgui-edit.r
			widgets		%rebgui-widgets.r
			requestors	%rebgui-requestors.r
			display		%rebgui-display.r
		][
			if none? word [set word do file]
		]
	]

	;if not value? 'edit [do %rebgui-edit.r]
	;if not value? 'widgets [do %rebgui-widgets.r]
	;if not value? 'requestors [do %rebgui-requestors.r]
	;if not value? 'display [do %rebgui-display.r]

	; export DISPLAY and the accessor functions to global context
	foreach word [display show-text show-data show-title splash][
		set word get in ctx-rebgui word
	]


  And each file no longer has a *named* context:

  --- edit.r ---

	REBOL [...]
	
	context [...]


  The above changes should mean few changes to the rebgui code. For 
  example, the body

  of the display function refers to the widgets context, but this is 
  still accessible
  because both DISPLAY and WIDGETS are inside ctx-rebgui.

request-dir

We have request-date for that. Spinners are usually used to increment 
/ decrement integers and percentages, with support for min, max and 
step values.

request-date give you a hudge over see spinner date give you a close 
contrôle for short time periode since now/date

for example Image I'm a commercial I need to set for tomorow a schedule 
with some client what would be grphically better for me ? click add 
button and then select the date user request date or Click Add button 
then use spinner to select the proper date and time and enter an 
entry to the topic field :)

Perk the translucent window capability is anOS feature that I request 
since lot of time but the key point is that this function is only 
accessible for some OS and for Linux it's a enligntenement layer 
(doesn't work with other X11 based windows manager ) example eterm 
is translucent but works only with enligtenment windows manager (the 
ones that comes with gnome )

Latest build available at: http://www.dobeash.com/files/RebGUI-031.zip


*** Unzip this file into your existing RebGUI 0.3.0 distribution. 
Requires View 1.3. ***

Highlights include:


 - Replaced scroller & slider widgets with Anton's new combined slider
	- Updated widgets to use same and set dragger size
	- Tab-panel now accepts actions (to enable dynamic tab displays)
	- Improved text-list selection logic
	- Prototype request-dir function added (needs a lot more work)
	- Large number of bug fixes
	- http://www.dobeash.com/it/rebgui/display.htmlupdated

Known issues:

	Unchanged.

On the drawing board

	Unchanged.

Anton

 1) Code size. What it loses in code size it gains in aesthetics and 
 simplified behaviour (check out the request-color and request-date 
 actions in %tour.r to see the extra "state" code required by the 
 original implementation). I like Brian's base64 solution.

 2) Tab-panel color: I've based this on the WinXP color scheme. Try 
 changing it to colors/window, it just doesn't look right. But slider 
 can be used on a colors/widget or colors/window background. WinXP 
 solves this by using a gradient / edge so that it is distinguishable 
 on either. So for RebGUI, a number of solutions are possible:

  - add a new colors/slider background that "works" with both widget 
  and windows background colors

  - add a new colors/tab-panel background that "works" with both widget 
  and windows background colors

  - use an effect like gradient to distinguish the slider background 
  color
		- or edge
		- or?
	I'm open to suggestions on this one. ;)

Brian
	1) I like the in-line image solution

 2) I like the base 64 solution even better! One problem, the button-down 
 image renders the same as button-up (i.e. 1st and 2nd images render 
 the same ... even though a quick glance at the data suggests they 
 are different?)

Graham
	Any examples where the desired behaviour is used?

shadwolf

 I did the same (replaced scroller call with "slider data [arrows]") 
 for text-list / table and it worked fine for me. Check for code that 
 tried to reference sub-faces in the old scroller widget (as Anton 
 refactored slider to use just one face).

Latest build available at: http://www.dobeash.com/files/RebGUI-034.zip


*** Unzip this file into your existing RebGUI 0.3.0 distribution. 
Requires View 1.3.1 ***

Highlights include:

	- request-dir requestor updated
	- alert and question requestors added

 - Tab focus expanded to include edit-list handling (see %focus-demo.r 
 for details)
	- Button image now resizes correctly

 - text-list widget totally rewritten to use [newly documented] View 
 1.3.1 iterated faces
	- text-list now supports Ctrl+click, Shift+click, Ctrl+A

 - text-list scrollbar now reacts to current display state (eg. disappears 
 if not required, alters dragger ratio as rows are added, etc) 
	- check and radio widget aesthetics improved

 - added options support to layout function and text-list and check 
 widgets

 - changed base-size from 4x5pixels to 5x4 pixels (better granularity)
	- reworked all widget sizes to account for above
	- fixed scaling problems with many widgets
	- updated focus-demo.r

 - greatly enhanced and expanded %tour.r to demonstrate more variations 
 and usage cases
	- added "live" unit-size and font-size drop-lists to %tour.r
	- numerous other minor bug fixes and coding improvements

In the works


 - table widget being rewritten along the same lines as the new improved 
 text-list widget
	- aiming for a 0.4.0 beta release prior to DevCon2005

Good first cut. I''d standardize label / field widths with composed 
words; eg.

window-size: NxN
tab-size: window-size - NxN
label-width: N
field-width: N

display "Test" compose [
	...
	label (label-width) ...
	field (field-width) ...
	...
]


This way you can globally experiment with different sizing layouts 
without too much effort.


If you come across anything that would make writing an app even easier 
(be it a RebGUI usage hint or enhancement request) then be sure to 
mention it here. Thanks. ;)

nice work on request-dir!

Any reason why request-file has lost the /keep refinement ?

Rebgui redefines 'request-file without the /keep refinement

Ashley - why request-date was redone? It has strange metrics here 
... too wide (x axis) and it looks like 80ies jurrasic Win3.1 period 
with btns :-) - old look was much nicer with chevron kind of buttons 
... and it was merely the same size X and Y axis wise ...

So, you should be concerned about not doing heavy computation inside 
network event callbacks (like in 'on-received). If longer processing 
is needed, you should use the task-master service in Uniserve to 
send the request to a slave process (this has also the advantage 
of fully using the power of modern multicores processors).

To determine if you can leave the work inside the callback, just 
do some simple maths. E.g., if a request needs 50ms to be processed, 
that means that your server cannot do more than 20req/s. So it also 
depends on the load your server need to handle.

I've got Univserve/cheyenne running on localhost.  I want my client 
to ask uniserve to download a file using one of it's processes and 
then play it through a sound port.  My client uses a http request 
and wants that to be non blocking ie. return immediately.  The client 
may itself not be capable of doing an async request.

eg. 
client => read http://localhost/speak.rsp?txt=helloworld

speak.rsp
<% 

 data: read/binary http://somewebserivice/cgi-bin/to-wave?text=helloworld
	insert sound-port  data
%>
<html></html>


in this scenario the client has to wait for the response.  How would 
one send the empty result back immediately, and then process the 
request so that the client is not blocked and where the client is 
incapable of an async read

By the way, old HTTPd service (in 0.9.9 zip) runs well for HTML pages.
But gives following error when I request show.cgi file:

btw, i will not send the payment request immediately. no need for 
that right now; (especially the banquet). but, please hurry if you 
want an hotel reservation! the sooner you register, the more time 
we have to arrange things and so on.

Please note, that Paypal request is sent in "Italiano" (forza Italia, 
I tutti quanti ;-) except the small text you have wrote to explain 
the request.

I had it without indexes at first , and later added indexes while 
I was trying various things, at 180 records there wasn't any noticable 
change. Well the result doesn't seem so bad to me right now.. if 
it has the same delay with 4000 records it's okey-ish. On my local 
computer which is much better than some small VPS I noticed no delays. 
I just realized that the delay at web-app was 3x bigger than this 
because I have 3 bots and each has it's own "mailbox" ... The solution 
for this situation will be affloading the inserts from the request 
process, for the future when things will need to scale up I will 
try doing this different anyway, that's why I was playing with actor 
like systems anyway

If you had persistent connection and if sqlite does some caching 
it could be faster, but if you need to open a connection on each 
request I think it would be much slower because that is more expensive 
(I assume).. it probably also matters how many scripts do you need 
to run per request

I do agree with Graham here - unification does make sense imo. The 
only "trouble" I see is, how you distinguish what is the cause of 
'none - is it returned as a legitimate value, or because of non-existant 
element request or other kind of "error"?

geomol:)) OK but if I will, who's going to finish this? http://bolek.techno.cz/pix/app/request-color.png
;-)

It's not a short paste...
[HTTPd] ================== NEW REQUEST ==================

                                                         [HTTPd] Request Line=>GET /testapp/ HTTP/1.1

                                                                                                     [HTTPd] Request Headers=>
Host: localhost:8080

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070310 
Iceweasel/2.0.0.3 (Debian-2.0.0.3-1)

Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive


[HTTPd] Phase url-to-filename done ( mod-alias )

                                                [HTTPd] Phase url-to-filename done ( mod-rsp )

                                                                                              [HTTPd] Phase url-to-filename done ( mod-fastcgi )
   [HTTPd] Phase url-to-filename done ( mod-static )

                                                    [HTTPd] Phase access-check done ( mod-action )

                                                                                                  [HTTPd] Phase set-mime-type done ( mod-action )
    [HTTPd] Phase make-response done ( mod-rsp )

                                                [HTTPd] Response=>

                                                                  HTTP/1.1 302 Moved Temporarily
Server: Cheyenne/0.9.11
Connection: close
Location: /testapp/login.rsp


[HTTPd] Phase logging done ( mod-static )

                                         [HTTPd] Phase clean-up done ( mod-rsp )

                                                                                [HTTPd] Connection closed

[HTTPd] ================== NEW REQUEST ==================        
                                        /

                                                         [HTTPd] Request Line=>GET /testapp/login.rsp HTTP/1.1

                                                                                                              [HTTPd] Request Headers=>
Host: localhost:8080

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070310 
Iceweasel/2.0.0.3 (Debian-2.0.0.3-1)

Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive


[HTTPd] Phase url-to-filename done ( mod-alias )

                                                [HTTPd] Phase url-to-filename done ( mod-rsp )

                                                                                              [HTTPd] Phase url-to-filename done ( mod-fastcgi )
   [HTTPd] Phase url-to-filename done ( mod-static )

                                                    [HTTPd] Phase access-check done ( mod-action )

                                                                                                  [HTTPd] Phase set-mime-type done ( mod-action )
    [HTTPd] Phase make-response done ( mod-rsp )
[HTTPd] Response=>
                  HTTP/1.1 200 OK
Server: Cheyenne/0.9.11
Content-Length: 482
Content-Type: text/html
Connection: Keep-Alive

Set-Cookie: RSPSID=EISPOMAZTPDFKVIWJAFONZDE; expires=Sat, 02 Jun 
2007 11:54:30 GMT; path=/testapp; HttpOnly
Pragma: no-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT


[HTTPd] Phase logging done ( mod-static )

                                         [HTTPd] Phase clean-up done ( mod-rsp )

                                                                                [HTTPd] Phase task-done done ( mod-rsp )

[HTTPd] ================== NEW REQUEST ==================        
                                                       \

                                                         [HTTPd] Request Line=>POST /testapp/login.rsp HTTP/1.1

                                                                                                               [HTTPd] Request Headers=>
Host: localhost:8080

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070310 
Iceweasel/2.0.0.3 (Debian-2.0.0.3-1)

Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://localhost:8080/testapp/login.rsp
Content-Type: application/x-www-form-urlencoded
Content-Length: 23


[HTTPd] Phase url-to-filename done ( mod-alias )

                                                [HTTPd] Phase url-to-filename done ( mod-rsp )

                                                                                              [HTTPd] Phase url-to-filename done ( mod-fastcgi )
   [HTTPd] Phase url-to-filename done ( mod-static )

                                                    [HTTPd] Posted data=>login=test&pass=letmein

                                                                                                [HTTPd] Phase access-check done ( mod-action )
 [HTTPd] Phase set-mime-type done ( mod-action )

                                                [HTTPd] Phase make-response done ( mod-rsp )
[HTTPd] Response=>
                  HTTP/1.1 301 Moved Permanently
Server: Cheyenne/0.9.11
Connection: close
Location: /testapp/

Set-Cookie: RSPSID=YDADUIONKJPHLFBWEDZDFCXN; expires=Sat, 02 Jun 
2007 11:54:37 GMT; path=/testapp; HttpOnly


[HTTPd] Phase logging done ( mod-static )

                                         [HTTPd] Phase clean-up done ( mod-rsp )

                                                                                [HTTPd] Phase task-done done ( mod-rsp )

                                                                                                                        [HTTPd] Connection closed
    [HTTPd] ================== NEW REQUEST ==================

                                                             [HTTPd] Request Line=>GET /testapp/ HTTP/1.1

                                                                                                         [HTTPd] Request Headers=>
Host: localhost:8080

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070310 
Iceweasel/2.0.0.3 (Debian-2.0.0.3-1)

Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://localhost:8080/testapp/login.rsp


[HTTPd] Phase url-to-filename done ( mod-alias )

                                                [HTTPd] Phase url-to-filename done ( mod-rsp )

                                                                                              [HTTPd] Phase url-to-filename done ( mod-fastcgi )
   [HTTPd] Phase url-to-filename done ( mod-static )

                                                    [HTTPd] Phase access-check done ( mod-action )

                                                                                                  [HTTPd] Phase set-mime-type done ( mod-action )
    [HTTPd] Phase make-response done ( mod-rsp )

                                                [HTTPd] Response=>

                                                                  HTTP/1.1 302 Moved Temporarily
Server: Cheyenne/0.9.11
Connection: close
Location: /testapp/login.rsp


[HTTPd] Phase logging done ( mod-static )

                                         [HTTPd] Phase clean-up done ( mod-rsp )

                                                                                [HTTPd] Connection closed

                                                                                                         [HTTPd] ================== NEW REQUEST ==================

                     [HTTPd] Request Line=>GET /testapp/login.rsp HTTP/1.1

                                                                          [HTTPd] Request Headers=>
Host: localhost:8080

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070310 
Iceweasel/2.0.0.3 (Debian-2.0.0.3-1)

Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://localhost:8080/testapp/login.rsp


[HTTPd] Phase url-to-filename done ( mod-alias )

                                                [HTTPd] Phase url-to-filename done ( mod-rsp )

                                                                                              [HTTPd] Phase url-to-filename done ( mod-fastcgi )
   [HTTPd] Phase url-to-filename done ( mod-static )

                                                    [HTTPd] Phase access-check done ( mod-action )

                                                                                                  [HTTPd] Phase set-mime-type done ( mod-action )
    [HTTPd] Phase make-response done ( mod-rsp )

                                                [HTTPd] Response=>

                                                                  HTTP/1.1 200 OK
Server: Cheyenne/0.9.11
Content-Length: 482
Content-Type: text/html
Connection: Keep-Alive

Set-Cookie: RSPSID=RTJSUKAVYBNOLCJCJBSTNUHP; expires=Sat, 02 Jun 
2007 11:54:37 GMT; path=/testapp; HttpOnly
Pragma: no-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT


[HTTPd] Phase logging done ( mod-static )

                                         [HTTPd] Phase clean-up done ( mod-rsp )

                                                                                [HTTPd] Phase task-done done ( mod-rsp )

I've been playing.

login.rsp

<%
	user: "test"
	pass: "letmein"

        print [<html> <body> <pre>]
        help request
        help request/content
        help session
        help session/content
        print [</pre> </body> </html>]

	in-user: select request/content 'login
	in-pass: select request/content 'pass
	
	if all [user = in-user pass = in-pass][
		session/content/login?: yes
		response/redirect "/testapp"
	]
%>

REQUEST/CONTENT is a block of value: []

Everytime through...first time and after filling in the login form.

My working login.rsp script ...

<%
		in-user: select request/content 'login
		in-pass: select request/content 'pass
		encoding-salt: to-binary "My encryption string"


  print [ <p/> "Login is: " in-user " and pass is " in-pass <p/> ]
				
		encode-pass: func [
			pass [string!]
			salt [binary!]
		] [
			checksum/secure append to binary! pass salt
		]

		
		if all [ in-user in-pass ][
			print <pre>


   qry: rejoin [ {select staffname, sid, fullname from staff where staffname 
   = '} in-user {' and pwd = '} form encode-pass in-pass encoding-salt 
   {'} ]

			probe qry
			print </p>
			
			sql: do-sql 'remr qry 
			print [ "Query result: " sql ]
			print </pre>	
			if found? sql/1 [
				response/redirect "/testapp/"
			]
		]
%>

Hmm...  request/content is empty on response/redirect "anything" 
everytime.

Changed to

response/redirect "/show.rsp"  (out of the testapp dir, to www/show.rsp) 

No request variables,
no session...

then I would say use any tool that permit you to see the header request/response, 
look closely what working websites sen in the response header for 
set-cookie change the mod-rsp to send the same apart from the RSPSID=xxx 
, eg remove path and expiration date

Hello again.  Tried the following...

dev [
    root-dir %www/
    default [%dev.rsp %dev.cgi %dev.html]
]

added to httpd.cfg  (dev is  192.168.1.102 in /etc/hosts)

%dev.rsp is
<html>
<head>
	<title> Manual Sessions</title>
</head>
<body>
<img src="logo.png">
<center>
<h2>Manual session mode</h2>


<% help session  help request session/start  help session response/redirect 
"show.rsp" %>
 
<BR><BR>Your ID is :  <%=session/id%><BR><BR>

<a href="show.rsp">Test RSP script</a>
</center>
</body>
</html> 

%raw.r is
REBOL []

port: open tcp://dev:8080
insert port {GET / HTTP/1.1
Host: dev:8080
User-Agent: REBOL/Core
Connection: close

}
result: copy port
close port
print result

Output is
>> do %raw.r
Script: "Untitled" (none)
HTTP/1.1 301 Moved Permanently
Server: Cheyenne/0.9.11
Content-Length: 1625
Content-Type: text/html
Connection: close
Location: show.rsp

Set-Cookie: RSPSID=IOERCVPFSDASSCXECGDFCTFG; expires=Sat, 02 Jun 
2007 19:54:16 GMT

<html>
<head>
    <title> Manual Sessions</title>
</head>
<body>
<img src="logo.png">
<center>
<h2>Manual session mode</h2>

SESSION is an object of value:
   content         none!     none
   timeout         none!     none
   events          none!     none
   id              none!     none
   active?         logic!    false
   init?           logic!    false
   add             function! [name [word!] value /local pos]
   remove          function! [name [word!]]
   exists?         function! [name [word!]]
   start           function! []
   reset           function! []
   end             function! []

REQUEST is an object of value:
   content         block!    length: 0
   headers         block!    length: 6
   method          word!     GET
   posted          none!     none
   client-ip       tuple!    192.168.1.102
   server-port     integer!  8080
   translated      file!     %www/dev.rsp

   parsed          object!   [headers status-line method url content 
   path targe...
   config          block!    length: 4
   web-app         none!     none
   query-string    function! [/local out]

SESSION is an object of value:
   content         block!    length: 0
   timeout         none!     none
   events          none!     none
   id              none!     none
   active?         logic!    false
   init?           logic!    false
   add             function! [name [word!] value /local pos]
   remove          function! [name [word!]]
   exists?         function! [name [word!]]
   start           function! []
   reset           function! []
   end             function! []


>>

Output from a Ice Weasel  http://dev:8080       - dev.rsp redirects 
to show.rsp...
Back

Timestamp: 2-Jun-2007/19:37:48-4:00

Request parameters :

    * HTTP Method: GET
    * HTTP Port: 8080
    * Client IP address: 192.168.1.102

Request headers :

    * Host : "dev"

    * User-Agent : {Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) 
    Gecko/20070310 Iceweasel/2.0.0.3 (Debian-2.0.0.3-1)}

    * Accept : {text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5}
    * Accept-Language : "en-us,en;q=0.5"
    * Accept-Encoding : "gzip,deflate"
    * Accept-Charset : "ISO-8859-1,utf-8;q=0.7,*;q=0.7"
    * Keep-Alive : "300"
    * Connection : "keep-alive"

Request variables :

    * No variable passed

Session :

    * No session

#[object! [ code: 311 type: script id: invalid-path arg1: config 
arg2: #[none] arg3: #[none] near: [request/config: value] where: 
decode-msg ]]

## Error in [task-handler] : Make object! [
    code: 311
    type: 'script
    id: 'invalid-path
    arg1: 'config
    arg2: none
    arg3: none
    near: [request/config: value]
    where: 'decode-msg
] !

Nenad, which modules are required for basic operation?  I'd like 
to build a single module that intercepts every request.

This certainly seems to kill cheyenne

## Error in [task-handler] : Make object! [
    code: 311
    type: 'script
    id: 'invalid-path
    arg1: 'config
    arg2: none
    arg3: none
    near: [request/config: value]
    where: 'decode-msg
] !

Graham: you crashed the RSP engine. Have you changed the meaning 
of the REQUEST word! ?

I'll add some protection to vital words (request, response, session, 
...) in the next release.

this line is for testing in mode-rsp/make-response if the request 
should be processed by mod-rsp or not.

Cheyenne release v0.9.12 beta. Download at http://softinnov.org/tmp/cheyenne-r0912.zip

Changelog :


 o do-sql function improved to support RT's DB drivers. /flat refinement 
 is 
	  supported now too. ODBC insert error fixed too.
	
	o RConsole prompt changed to "Server>"
	
	o CGI's 'path-info now returns the request URL.
	

 o Fixed a bug in RSP session destruction potentially corrupting the 
 internal 
	  session list and giving weird results or behaviour.
	  

 o Fixed a timezone computation bug that was setting incorrect expire 
 times for 

   session cookies, resulting in unstable behaviour. All platforms except 
   Windows.
	  

 o Small patch to parse-request-line func in HTTPd.r to be more 'mod-rewrite 
	  friendly.

do you 'do them at each request ?

How you detect that the page request is http and not https so that 
you can redirect the request?

A method to distinguish between SSL request (coming from stunnel) 
or normal HTTP request, is to make Cheyenne listens on 2 ports : 
80 and 443 (for example, could be any port <> 80) and configure stunnel 
to redirect the decrypted SSL traffic to port 443. Then in your RSP, 
request/server-port will tell which port was used to receive the 
request. Example :

switch request/server-port [
	80  [...normal HTTP traffic...]
	443 [...SSL traffic...]
]

Cheyenne release v0.9.13 beta. Download at http://softinnov.org/tmp/cheyenne-r0913.zip

Changelog :


 o Session cookie management refactored. Cookies are now cached in 
 memory. 
	  Fixes all issues related to timezone.
	  

 o HTTPd request pipeline refactored. It's now more reliable, little 
 faster and

   able to handle extreme situations (stressing with FasterFox). Several 
   core parts
	  of Cheyenne have been touched, so watch out for regressions.
	  

 o Added 'forward method to RSP's Response object (now possible thanks 
 to the 
	  new pipeline engine).
	  

 o Internal modules API changed : 'deferred? property removed (not 
 needed 
	  anymore with new pipeline).
	  

 o Added 'on-status-code option in config file (see example in %httpd.cfg).
	  

 o do-sql now catches internal errors, so they can be more easily 
 located in 
	  calling context.

Now the url looks okay at the top, but the request url is wrong

also the values in the request content show up with double quotes

Quick patch for url-encoded value bug: 

1: in %HTTPd.r find the 'parse-request-line function
2: change the following line :

    parse/all dehex ctx/status-line: copy line [
to
    parse/all ctx/status-line: copy line [

3: change the following line :

    ctx/url: path: trim url
to    
    ctx/url: path: dehex trim url

Cheyenne release v0.9.14 beta. Download at http://softinnov.org/tmp/cheyenne-r0914.zip

Changelog :

o response/forward improved : 

 - fully supports URLs as argument (can now forward to another virtual 
 host).
	- URL validity check (must have an explicit target).
	- protection against cycles.


o Command line option -p extended, now you can specify several listen 
ports separated
   by a comma (ex: -p 80,10443).


o New command line option -e : load and initialize Cheyenne without 
entering the

   event loop (needed for embedding Cheyenne in third party apps).


o Added a new experimental module: mod-embed. Purpose is to allow 
easy Cheyenne

   integration in third-party REBOL applications that require an embedded 
   web
   server. (Uncomment mod-embed in httpd.cfg file to activate it)


o Added %embed-demo.r file to show a sample of the mod-embed usage 
and API. 

o RSP: <% without %> eats all the memory. Fixed.

o URL-encoded request values were not parsed correctly. Fixed.


o RSP: fixed a typo in 'decode-params blocking the multipart data 
decoding and
   also a local word ('type) leaking in GC.

o UniServe's service startup refactored to be more flexible.



The new mod-embed is experimental. Please look at the %embed-demo.r 
file and send your feedbacks here.

hmm.. followed the instructions.. uncommented the httpd.conf (need 
to comment out the others??)

[uniserve] Async Protocol FastCGI loaded
[uniserve] Starting task-master...
[uniserve] Starting HTTPd...

## Error in [uniserve] : On-received call failed with error: make 
object! [
    code: 303
    type: 'script
    id: 'expect-arg
    arg1: 'in
    arg2: 'object
    arg3: [object! port!]
    near: [if in site 'on-request [
            if site/on-request req params svc [return true]
        ]]
    where: 'handler
] !

If the session ID is persistent in a DB any Cheyenne can handle the 
request

Terry: that's the intended behaviour, if you request /testapp, it 
calls the 'testapp function in root object (or 'default func if 'testapp 
is not defined), it you request /testapp/, it calls the 'default 
function in the 'testapp object. But that's the demo "site", you 
can change the behaviour in your own "site" if it doesn't fit your 
needs.

well, I have this:

probe request/content
	street1: url-encode any [ select request/content 'street1 "" ]
print <br/>	
?? street1
print <br/>

probe dehex street1
print <br/>

mod-router - a module that routes request based on a sitemap

mod-router: you mean being able to translate the request URLs for 
a whole site, based on a sitemap description ?

Hey Doc, thanks..
One thing I was trying with Uniserve years ago went like this.. 
1) A http request is received as usual. (port 80)

2) Depending on the request, Uniserve would launch a process that 
may run for hours (ie: reading a website looking for changes), and 
would occasionally send a message back to the ip address, but on 
a different port (communicates to a flash script on the original 
response page, that in turns manipulates the DOM.)


So, what's the best method to run these small scripts as to not block, 
and close without closing the server. 

I still want to serve up an HTML response, so it's a hybrid of sorts.. 
sends back a page AND runs it as a handler too?

UniServe is based on the classic request/response model. You have 
to implement a specific UniServe' service for your specific need 
(like sending a response to another client than the one who sent 
the request). I guess you'll have to maintain in the service's context 
a list of the (browser, flash) connections couples, so there's some 
probabilities that you'll end up write a full custom HTTPd service.

parse/all request/headers/Content-type [
			thru "boundary=" opt dquote copy bound [to dquote | to end]
		]
		if not bound [return ""]	 ;-- add proper error handler
		insert bound "--"	
		list: make block! 2
		parse/all data [
...

and measure.rsp is ..

<html>
<body>

<%
	either content: select request/content 'content [
		print [ <data> length? content </data> ]
	][
		%> Nothing was sent! <%
	]
%>
</body>
</html>

No tested, but I don't why this would be a problem for Cheyenne, 
as long as it's a valid HTTP request. There's only two upload encodings 
that Cheyenne currently doesn't support: multipart/mixed and chunked. 
Chunked encoding is only supported in Cheyenne's responses.

Cheyenne release v0.9.16 beta. Download at http://softinnov.org/tmp/cheyenne-r0916.zip

Changelog :

v0.9.16 - 12/07/2007
	
	o Localization framework added to RSP. API overview :
	
		- #[text] in static parts of RSP pages will be translated.
		

  - new function: say "data" : translate a string! value in the current
		  language.
		  
		- session's new 'lang variable can set the current language.
		
		- new config file options to control default language and 
		  locales resources folder.
		

 o Decode-cgi rewrote from scratch. Cleaner and 2-3 times faster than 
 before.
	

 o RSP request params decoding rewrote. Now GET and POST parameters 
 are unified
	  in request/content.
	  
	o BugFix for encapping %misc/mime-types file.
	

 o File upload support redesigned. Now big files (user defined threshold) 
 are

   directly written to disk in temporary files, instead of being held 
   in memory.

   The temporary files are deleted once the request is completed. So 
   now

   Cheyenne supports files upload up to 2Gb (R2 port! limitation).
	  

 o CGI execution extended to any scripts (not just REBOL). If found, 
 the

   shebang line (#!) is honored (on all platforms). Several perl scripts
	  added in %www/ folder as demo.
	  

 o Module's 'on-started event now fired only once, when multiple HTTPd 
 instances
	  are listening on more than one port.
	  

 o New module : mod-extapp for launching and managing external applications.

   Only the start and shutdown actions are currently supported. Load 
   balancing
	  will be included in future.
	
	o FastCGI protocol reliability improved and some bugs fixed.
	
	o RSP-API documentation updated.

Yeah, QM conflicts with  request  and Vanilla conflicts with  session 
 (at the quick glance I've taken so far).  These types of problems 
are pretty easy to fix given the motivation.  REBOL is eminently 
readable; all it requires is a little motivation, time and judicious 
use of context or global find and replace.  Collisions are always 
hit or miss, but the web related scripts usually collide just by 
nature of the higher level words being the perfect words for the 
concept at hand.   People running Apache would never see these collisions.


R3 holds a lot of promise in allowing us rebols the freedom for independent 
development that others can combine in fun and magical ways, worry 
free of this issue.  Another year and this type of complaint should 
be a thing of distant memory.

I'm not sure to understand the issue with Cheyenne CGI ? For RSP, 
there's a list of global words that MUST not be modified like : request, 
session, response... If you want to use, in RSP code, a framework 
that will conflict with RSP words in global space, you'd better wait 
for R3 to cleanly handle those issues, R2 namespace managment is 
just too limited.

protect [
	do-sql db-cache request response session include
	include-file validate locale say
]

RSP is the best way and the faster inexecution/response time (instead 
of Apache cgi, it doesn't need to load rebol and your init library 
at each request), to do dynamic stuff with Cheyenne. The API is very 
sleek and you can read about it in the downloadable documentation 
part of Cheyeene download.

C struct for device request