AltME groups: search

Run is done by RebolTof, Belgium developper, who works for Belgium's 
army.
So RUn was develop and is used in real case.


He has also done RAPId (Rebol API Documentor), a JavaDoc like Document 
generator for Rebol
 https://sourceforge.net/projects/rapid/


For the english doc, contact him directly [christophe-:-coussement-:-mil-:-be]

Graham, right, I need to access the tape. The next problem is to 
handle things like: open-files, system state for Windows machines 
etc. IIRC Windows provides an API for backup-programs. If you want 
to do live backups of things like running DBs or Exchange etc. you 
need special APIs as well.

Brock, the app has an API to its own "flat file" database ... mainly 
blocks of REBOL objects.

On each update transaction (which usually affects several flat files) 
we record the before images.

That makes Undo really just the same as a Rollback.


The Undo log keeps the last 100 (or a user selectable number of) 
transactions, so they can go back a long way if they need to.


But,. like a lot of things, the code was experiemental and as such 
is a pile of kark. One day, I might tidy it up into an API undertstandable 
by someone other than me,  It the meantime, I that's enough high-level 
clues to help you replicate the logic.

Good input. Petr, try to find out what it would need to code such 
an API with a scripting language. Just to get a better picture about 
the problem domain.

target the Series handphones. eg Series 60, from Nokia.


isn't that the key idea for those 'Series' handphones from Nokia. 
..so that developers can have single API to develop on and easily 
 deploy on a large enough 'market share'

Besides that, IIRC Carl told us in the past, that currently what 
you find as a rebol component (look into system object), is already 
internally modular, so who knows - maybe it already goes via some 
abstraction api

Well, there you go. Look in MSDN in the Office API section.

A closer look and no it does not.  I got some of the input and output 
formats confussed.  I thought it could read from a SQL/ODBC data 
source but appears that is only an output format.  There is a COM 
api, but that might be more complex than is worth.

As for the code golfing, it might also be a good idea to use popular 
topics as a theme. A puzzle that makes use of an API like Twitter, 
YouTube, Flickr, Facebook etc. REBOL seems to be pretty good in the 
internet/Network department, so why not make use of it? Those websites 
are popular for a reason. This could also end up producing some more 
libraries to easily use REBOL with popular APIs.

rebol tutorial has a twitter api under 10 lines IIRC

is it possible to have an API for altme where we can do things such 
as online backgammon via altme?  Its the perfect lobby setup :)

As far as i can tell, the files stored under the world name show 
only when a user joined and when they last posted.

Clearly, AltME is sending connection information -- we can all see 
that if we sort the Users list by Status. But is there an API to 
access that? There may be an answer available here :-)
http://www.altme.com/feedback.html

I hate Vista....

Anyone else have this prob:


Using altme to share many files. I see them in altme but they do 
not exist in the proper altme file folder.


From what I've gathered Vista with UAC enabled (default) does not 
allow programs that do not comply with their new security API to 
write to certain folders such as "program files" whrere Altme is 
installed.


So if I try to open it with notepad, notpad can not see it as it 
does not really exist in that folder that altme tells notpads that 
its in. Vista re-routes altme to the "safe" location without altme 
knowing this.

Anyone have a work around...


I could turn off UAC but that is suppose to be bad (security reasons).


I guess I could move altme to a non secure folder (not sure what 
that would be? I think the Desktop has the same issues...
maybe just C:??

I'm using this feature in the OpenGL API, I'm working at. Maybe I 
could do a late reduce, when accessing the inner blocks.

james, no C syntax. I'm making a REBOL version of the OpenGL API 
with REBOL syntax. Users will be able to use normal REBOL and call 
OpenGL functions (with REBOL syntax).

John, Is your opengl api rendering in a rebol window or face?

using the win32 api

I wonder why using the windows 32 api, I still can't set the user 
environment variables

You can do it using Windows API...

what two apis? set-style/get-style is cool api, I just say it should 
be extended. If designer asks me to expose change of backcolor, I 
will do internally to my style whatever is needed, and expose it 
via set-style 'back-color value. Facets are different thing - they 
are dialect related, you can (or don't need to) expose 'back-color 
as a facet to allow its usage directly via VID code ...

one api is vid. You knw i can face/text there, foreground, background 
etc already.

No one except playing with Win32 API (good luck)

For Always-on-top, nothing else than digging in Win32 API !!

For system tray, may be this example can help understanding its usage

http://www.rebol.org/cgi-bin/cgiwrap/rebol/view-script.r?script=simple-system-tray.r

I think thare are two slightly different goals. One is to deal with 
the main data in a face. That should be a single value. The other 
is to make a snapshot of a layout, save it, qui script, and reload 
it later. I like that behavior. And i am not sure a single value 
is sufficient for that. But it would be an internal thing about saving, 
as api i prefer something with more defaults, ala VID.

It should be possible. It's a parameter to the ShellExecute and SetWindowPos 
API functions.

And not just Flash - http://www.applecore99.com/api/api012.asp

you would have to use win32 api imo ....

there is also glayout, which works very out of the box and is built 
over VID.  the api isn't document though.


you can look at the glayout-demo app on rebol.org so have an idea 
of all it can do.  it layout engine is very complete, and seems like 
the basis for how R3 was implemented... they use the same philosophy.


glayout handles ALL resizing automatically, and it even includes 
real scrollpanes, which react to content, as it changes (scrollbars 
resize automatically, for example)

I plan to write an R2 chat client this month (with as much help as 
is made available). At first it will be a clone of R3 chat, but there 
is nothing in the DevBase server API that requires the clients to 
be in text mode.

... need of a draft about all the api to exchange with the server

If you can help, Steeve, or even get started on it yourself, go for 
it. I don't think there is an API doc yet - the API changes too much.

Thanks Nick!


If AltME had an API that allowed us to write messages into a world, 
then perhaps we could use that to have a write-also interface to 
the AltME archive at REBOL.org, in addition to the read-only interface 
we see now. 

Ditto, a mailing list API.

But we'd need the APIs first :)


And I can immediately see various issues related to preventing spam 
and bots from rampaging through those APIs ... But not insurrmountable. 


Clearly, this is not an issue for [I'm New] -- perhaps switch to 
[Script Libary] for any further comments,

REBOL does not currently run _on_ any phones (that I know of) though 
this blog post offers some hope:
    http://www.rebol.com/cgi-bin/blog.r?view=0274


If you want to connect _to_ a phone from a REBOL-supported platform 
(Win, Lin, MAC, etc) then, as Henrik says, the crucial issue is the 
API to access the phone's functions. REBOL can probable connect to 
that API. But without more details, we'd be guessing.

The REBOL2 external library interface (ie how you might connect to 
an API) is described here:
    http://www.rebol.com/docs/library.html

Hello - hope someone can find the newbie mistake I'm making here. 
 Wanted to use REBOL to tackle a need to get data from Salesforce 
using their SOAP API.  New to SOAP, WSDL and Salesforce, but using 
SoapUI mananged to do this POST (edited only to hide personal info):

POST https://login.salesforce.com/services/Soap/u/19.0HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: ""
User-Agent: Jakarta Commons-HttpClient/3.1
Host: login.salesforce.com
Content-Length: 525


<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:partner.soap.sforce.com">
   <soapenv:Header>
      <urn:CallOptions>
         <urn:client></urn:client>
         <urn:defaultNamespace></urn:defaultNamespace>
      </urn:CallOptions>
   </soapenv:Header>
   <soapenv:Body>
      <urn:login>
         <urn:username>[jort-:-xxxxxxxxxxxxx-:-com]</urn:username>

         <urn:password>xxxxxxxxxx78l6g7iFac5uaviDnJLFxxxxx</urn:password>
      </urn:login>
   </soapenv:Body>
</soapenv:Envelope>

and get the desired response:

HTTP/1.1 200 OK
Server: 
Content-Encoding: gzip
Content-Type: text/xml; charset=utf-8
Content-Length: 736
Date: Fri, 02 Jul 2010 20:32:14 GMT


<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns="urn:partner.soap.sforce.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><loginResponse> 
......

Then using SoapUI I am able to send a successful Logout message.


Using REBOL 2.7.7.3.1, I created an "upload" string containing the 
POST block above without the "POST " at the beginning, set my url 
to:

>> url
== https://login.salesforce.com/services/Soap/u/19.0

and tried this:

>> response: read/custom url reduce ['POST upload]

but consistently get a Server 500 error:


** User Error: Error.  Target url: https://login.salesforce.com:443/services/Soap/u/19.0 
could not be retrieved.  Se
rver response: HTTP...
** Near: response: read/custom url reduce ['POST upload]

For completeness, here's the upload value:

>> print mold upload
{https://login.salesforce.com/services/Soap/u/19.0HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: ""
User-Agent: Jakarta Commons-HttpClient/3.1
Host: login.salesforce.com
Content-Length: 525


<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:partner.soap.sforce.com">

   <soapenv:Header>
      <urn:CallOptions>
         <urn:client></urn:client>
         <urn:defaultNamespace></urn:defaultNamespace>
      </urn:CallOptions>
   </soapenv:Header>
   <soapenv:Body>
      <urn:login>
         <urn:username>[jort-:-researchpoint-:-com]</urn:username>

         <urn:password>metrics12378l6g7iFac5uaviDnJLFVprDl</urn:password>
      </urn:login>
   </soapenv:Body>
</soapenv:Envelope>}

Would appreciate any help you can give!

But ... the saleforce.com api also allows http login for testing 
thru proxies.  I suggest you test against that and use wireshark 
to trace the transaction.

remark v1: uses series handling, funcs, and a lot of code to get 
it to work.  

prbably about 200 lines.

remark v2:   20 line parse rule + 5line stack context object.


v2 is 50 times faster, and does twice as more, while being much more 
flexible in many api aspects.


parse is powerfull, but it took me 4 years to understand parse well 
enough in order to rewrite remark.

I haven't gone over the code in SPLIT yet. Something about the API 
seems wrong, though not as bad as FORMAT. Once it iss more settled 
I'll backport SPLIT to R2 and put it in R2-Forward.

you can test real data as well:)

print "loading data"
data: read/string http://www.imagemagick.org/api/magick-image.php
ask "parsing version 1"
parse/all data [
	some [
	    thru {<h2><a} thru ">" copy name to {<}
	    doc-start: to {^/ </div>} doc-end: :doc-start
		[
	        thru {<pre class="code">} copy code to {</pre} (
	            probe name
	            probe code
	        )
	        any [
	            thru {<h5>}
				here: if (lesser? index? here index? doc-end)
				copy arg to {<}
	            thru {<ol><p>} copy arg-desc to {</p></ol>}
	            (printf ["  * " 10 " - "] reduce [arg arg-desc])
	        ] 
	    ]
	    :doc-end
	]
]
ask "parsing version 2"
parse/all data [
	some [
	    thru {<h2><a} thru ">" copy name to {<}
	    ; copy the DOC
	    copy doc to {^/ </div>}
		; remember the DOC-END
		doc-end:
		; switch to DOC parsing
		:doc
	    thru {<pre class="code">} copy code to {</pre} (
	        probe name
	        probe code
		)
	    any [
	        thru {<h5>} copy arg to {<}
	        thru {<ol><p>} copy arg-desc to {</p></ol>}
	        (printf ["  * " 10 " - "] reduce [arg arg-desc])
	    ]
	    ; switch to original input
	    :doc-end
	]
]

ok, so does the OS API mimic those from the Amiga?  (and would thus 
allow easier port of old Amiga sources)

btw - is there any plan for R3 clone? Most open source parts will 
be usable, API seems to be defined, so maybe cloning effort is easier 
now? Or don't you mind using 3rd party binary packages?

ap=api

The porting API of R3 isn't quite settled yet, and the library would 
have to be compiled for Syllable. Not a big problem.

The method, yes. The api and specs, still in process.

btw if i vidify rebgui, is there a chance to get it accepted? or 
do you insist on the api-clashes?

BTW, good spot Volker. As for your two questions:

1) If i vidify rebgui, is there a chance to get it accepted?


I'll except anything that makes writing a REBOL GUI (View, VID, RebGUI, 
whatever) easier. ;)

2) Do you insist on the api-clashes?

Not sure what the issue is here, please elaborate.

I just want to inform you what enhancements I needed and Cyphre did 
so far for RebGUI:


table: Add an API to table that allows to change the columns layout 
at runtime: my-table/set-columns ["Column 1" left 0.25 "Column2" 
center 0.75]


drop-list: fire action only if selection was made/changed, at the 
moment action fires if clicked on field too


general: on-un/focus should be fired if user clicks an other widget, 
not only if carets leaves the widget when TAB is pressed


table: moving bar up/down with keyboard should fire click-action, 
alternativ: pressing RETURN can fire click action

table: align header text like data (left, center, right) at the moment 
always left
table: TRAC #21


TRAC #5 Cyphre: should be fixed but please test it and let me know. 

TRAC #6

Tree: The code for the tree is mostly complete. Even an API to change 
the tree at runtime exists. The code isn't splitted out into a standalone 
tree-widget yet. It's included in the drop-tree widget.

ATTENTION: rebgui-edit.r was not yet merged. Latest revision doesn't 
include older changes. We will do this ASAP. But rebgui-edit.r is 
required in this version otherwise all other changes done by us might 
not work.



FIXED *rebgui/pad: Now only works for horizontal padding. Padding 
should happen depending on the layout direction left-to-right or 
top-to-down.
	Cyphre: now PAD works according to the AFTER settigns. Example:
	display "Test" [
		after 3
	    field
		pad 5
	    field
	    pad 5
	    field
	    pad 5
	    field
	    pad 5
	    field
	    pad 5
	    field
	]
	Robert,let me know if it works like you wanted.

FIXED *group-box: When setting a new title group-box/text: "new-title" 
the surounding frame needs to be adjusted to the new text-width.

FIXED *drop-tree: When selecting different quick-access buttons directly 
one after the other, the drop-tree shouldn't close

FIXED *drop-tree: Highlighting the pressed quick-access button with 
green, the hovered one as is in orange. To give user visial feedback.

FIXED *general: a way to sepcify "align ['left]" for all further 
widgets to avoide repeation. Idea: Add disaply keywords: left, right, 
center
	Cyphre: added keyword TEXT-ALIGN left/right/center. Example:
	display "Test" [
		text-align right
		after 3
	    t: text 20 "test 1"
	    field "test 2"
	    field "test 3"
	    text-align left
	    field "test 4"
	    field "test 5"
	    field "test 6"
	]

FIXED *drop-list: an option that will show the list layered above 
everything (like the tree list of drop-tree).
	Cyphre: added drop-list/popup-mode: 'inside(default) or 'outside
	note: the same works for drop-tree

FIXED *drop-tree: changing state of the drop-tree (a new entry was 
selected) should only be done if the ACTION code returns TRUE. Otherwise 
the old state is kept, the drop-tree is closed and nothing happens. 
This allows the code to check for some pre-conditions before changing 
the state, and give some feedback to the user. Much like the on-unfocus 
functionality of RebGUI.

FIXED *drop-tree: pressing the quick-access numbers doesn't work 
any more as the drop-tree closes now if the mouse is clicked outside 
the drop-tree

FIXED *table: table/selected returns NONE if the table is empty and 
no record is selected. If there was one recrod selected at any time, 
than table/selected returns [none none <repeated for number of columns>]. 
If not row is selected at any time, table/selected should just return 
NONE.

FIXED *table: If a table is re-used in that the table is reused with 
code like:
	insert clear table/data [...]
	people/redraw

and there was a row selected before, than the internal state is still 
in "row selected" but the new row isn't highlighted. Here internal 
state and GUI don't match.

FIXED *drop-tree: clicking a "+/-" in the tree only open/closes the 
tree without calling the action for the node

FIXED *drop-tree: Re-add whole line selection and hovering functionality 
(so that mouse does not have to be over text)

FIXED *drop-tree: Add an option to get big fast-selction keys aligned 
left-to-right
	Cyphre: added drop-tree/expander-mode: 'big(default) or 'small

FIXED *button: Add an option to disable a button my-button/active: 
true/false, if disabled the button is drawn greyed-out
	Cyphre: usage is my-button/active: true/false show my-button

FIXED *field: Support number datatypes for TEXT so that things like 
field-a/text + field-b/text can be used

 Cyphre: you need to set field/edit-mode: 'numbers to activate this 
 behaviour for field(othervise it works like a normal field)
	2nd implementation uses own styel: number-field

FIXED *radio-group: Add an API that allows to provide a new DATA 
specification block at runtime or a way to alter the text of the 
radio fields at runtime.

 Cyphre: now you can just change the data content and do show on the 
 radio-group like:
		my-radio-group/data: ["item1" "item2" "item3" "item4"]
		show my-radio-group

 Note that it won't react on change of number of items. Just change 
 of texts.

FIXED *radio-group: Add a way to select one radio field at run-time
	added accesor select-item item [integer!] usage:
		my-radio-group/select-item 2
		show my-radio-group

 note: you can get the selected item using my-radio-group/picked, 
 you can get the text of selected item using my-radio-group/selected

FIXED *drop-tree/grey-out: Can it be done in that we only show the 
text in a light grey instead of black? Like Windows does it.
	Cyphre: now the masked text is light grey

FIXED *on-focus / on-unfocus: If FALSE is return from the ACTION 
and the user clicked somewhere on the screen, the focus is still 
in the "field" but no cursor bar is visible

FIXED *drop-list: IIRC in your widgets it was possible to start typing 
and the selection list was filtered. A mandatory feature for the 
drop-list :-))

 Cyphre: added drop-list/editable? flag to enable/disable editing 
 of the drop-list field

 also added drop-list/auto-fill? flag which enables automatic text 
 filterin from the selection list

FIXED *general: add hover tooltip help option to every widget (global 
patch)

 Cyphre: added TOOL-TIP facet to rebface object. If TOOL-TIP is set 
 to string! value a tooltip is shown when mouseover such widget.
	example:
		display "test" [
			button "press me" tool-tip "press this button to continue"
		]

FIXED*drop-list: proivde a much better selection-list opening algorithm 
especially for long lists. Open upward, downward, middle like so 
that as much entries are shown for the given screen space. And an 
option that will show the list layered above everything (like the 
tree list of drop-tree).
	Cyphre:

 -added droplist/lines - can be 'auto (default) or integer! to force 
 number of shown lines in droplist

 -added droplist/droplist-mode - can be 'auto (default) 'upward, 'downward 
 or 'middle to force way how the list is popped up
	you can use various combination of those settings.
FIXED*table: Add an API that allows to select a row at run-time.
	Cyphre: Usage is for example:
		my-table/select-row 5
		show my-table

FIXED*table: Add an API to table that allows to change the columns 
layout at runtime: my-table/reset ["Column 1" left 0.25 "Column2" 
center 0.75]

 Cyphre: I added the functionality byt the API call is my-table/set-columns 
 ["Column 1" left 0.25 "Column2" center 0.75]

FIXED*drop-list: fire action only if selection was made/changed, 
at the moment action fires if clicked on field too

FIXED*general: on-un/focus should be fired if user clicks an other 
widget, not only if carets leaves the widget when TAB is pressed

FIXED*table: moving bar up/down with keyboard should fire click-action, 
alternativ: pressing RETURN can fire click action

FIXED*table: align header text like data (left, center, right) at 
the moment always left
FIXED*table: TRAC #21

FiXED*TRAC #5 Cyphre: should be fixed but please test it and let 
me know.
FIXED*TRAC #6

currently functions like - swap-columns, insert-column, remove-column, 
work with real data block, whereas sorting column introduces virtual 
adressing. You can still access raw data by going to grid/content/2/2 
or so, but if you want to get sorting reflected, you need to use 
API ....

And, I find it simpelst to have the data on the screen and in the 
program in sync. Sorting should alter the data block as well. If 
I pick the first line, I want to pick the first record. Of course 
using an API for indirection is OK too. But than do it always and 
for everything. No direct access to the record data.

Beer uses an api as outlined by Carl. So its one lns-implementation 
good enough to be published. Maybe the two could merge for the async 
daemon part.

As for lns development, I did a small lns emulation a while back 
based on published info. I found writing a service was easy, I think 
Gabriele demonstrated this well. I concluded that lns was a great 
idea, but there will be a learning curve of course. Reqesting the 
service from the client is a one-liner, but that is only the beginning 
of the story. Aside from the careful thought required in designing 
a service API, it will be interesting to see how people structure 
their client code because I think that is where the complexity of 
lns development could be from a programming point of view (e.g dealing 
with the service response).  Of course it depends on the application.

I mentioned certificates for two reasons here. 1) IIRC Holger (or 
someone from RT, do not remember right now) said, that internally 
Rebol has some parser for that, but the API for that is not exposed 
2) it seems to me, that there might be some parts of the world, where 
encryption is enough, and there is nothing bad with such opinion, 
in regards to such countries ...

Just a question: is there a way to let external fuctions (outside 
REBOL) be associated to a rebol word ? Could this fuction access 
REBOL values via some API ?

That was quick! Yet still don't get the 'range' part. I do understand 
the copy/part a 2, and the second copy/part next a 2. Maybe I don't 
understand how to interpret the API docs?

Gabriele, any plans to improve the library interface for R3, or even 
make it free so that more people use it (I don't think this affects 
RT sales b/c most companies buy solutions, e.g. FCGI or MySQL api, 
... )

this allows you to remove the complexity of an API and integrate 
it within the normal flow of a language.

they still boil down to pretty much the same thing... they could 
simple be the same api.

I think I meant to say that I hope the api, can be uniformitised... 
so we decide if we want instance or class based method.

Maxim, what does it matter if the API is uniform, as long as the 
syntax is similar? You can't make the API completely uniform when 
you are supporting different semantic models.

I'd just like more hooking capabilities right in the api.   just 
like Amiga allowed many things to be extended without needing to 
replace them.

and I am pretty sure the final will appeal to most who are working 
on module like api code.

I would like to be a part of the early access group, but not for 
VID. My GUI experience is founded in quite different environments 
and my input about GUIs would be more along the lines of API cleanup 
and other low-level stuff. For the major design issues, I defer to 
Carl, Gabriele, Cyphre and the other capable people here - I trust 
your judgement.


I would like to help with some of the other parts of REBOL 3 though. 
My main interests are in language design, interoperability issues 
and platform integration, particularly Windows platforms and derivatives 
since that's what I need to use most of the time.

Java does a good job of making platform-specific menus with a cross-platform 
API that requires no changes. It may be good to look at.

Well, once R3 comes out, the community will be helping with the platform 
implementation - RT will be focusing on the core of REBOL, and that 
has no UI at all, just an API. Remember which group you are asking 
this question in.

Commercial plugins - well, the API was introduced, no? Is it available 
in alpha?

SSL is specific protocol. I am not speaking about encryption here, 
but about the trust, that is what certificates are for. IIRC the 
api for them is inside, it was not just exposed. And IIRC2, Ladislav 
once mentioned he will do it? But I could misunderstood him ...

really? (re screenshot) ... moving windows by accelerator keys was 
fine. I think that we will need to map win32 api, which will tell 
us about particular monitor set-ups ...

yes, I used and a bit extended Gregg's keys dialect. I was able to 
shape and move windows by calling win32 api functions. I tried to 
wrapp also the monitor stuff, but if was upon my capabilities ....

yes, interesting. In fact, I am not that skilled to know the answer 
- under Windows, I once looked into API, and there seems to be some 
API for printing, however that has nothing in common with Postcript 
- you get bitmap area and then you somehow submit it to driver ...

Comes with a programmable API too

As I understand it, modules implemented the task-master API.  But 
now you have mods instead of modules, and instead of install-module, 
you have install-HTTPd-extension

I'm creating an API, and each api word maps to a single rsp page 
inside a %rest directory.  It is up to the rsp page to decide which 
actual function is being called, and to deal with all the parameters.

And also to deal with authentication.  Basic authentication will 
be used for each api call .. and the whole site will be behind https.

so, DELETE /@api/fax/jobno and GET /@api/fax/jobno both map to the 
same rsp page.

It's straight forward and you should see the default test page. If 
not, check your %httpd.cfg config file. They're no general documentation 
available yet, only RSP API is documented.

Btw, I've tried to use file locking method to be able to sync writes 
to the same file from several processes. None of the file locking 
code found on rebol.org works reliably enough. At best, all processes 
can write their content to the file, but the order is messed up (each 
line starts with a timestamp), so not usable in my case. I didn't 
want to try using OS native file locking API, I'm afraid that a frozen 
process could permanently lock the file and block all the other processes, 
so it's too risky (at least using only REBOL, I could have some escape 
strategy to avoid that).

just to say that I am still working on cheyenne based web-app .. 
I find cheyenne rsp api very well designed, everything is obvious 
and simple.. I will put out some sources of the tools I built to 
help me develop, nothing special but maybe can come handy to someone

Thanks Janko, the RSP API is very inspired by other APIs like ASP 
and JSP, so most of the credits goes to Microsoft and Sun ;-).

Will: that is exactly what I did when I tried to use it and saw the 
workflow/api very nice, then I tested the req/sec and I astonished 
reported here :) (1 month or so back)

Btw, if you don't know how to build RSP scripts, you should first 
have a look at ASP or JSP online documentation, so you can get the 
concept and usage. RSP API can be found on http://cheyenne-server.org/docs/rsp-api.html

7/3-21:59:42.822-## Error in [OS-API] : OpenSCManager failed : Access 
is denied. !
7/3-21:59:42.826-[boot] Cmdline args : -v
7/3-21:59:42.835-[boot] Processed    : [verbosity 1]
7/3-21:59:42.838-[boot] Boot flags   : [verbose]

7/3-21:59:42.840-[boot] Data folder  : %/C/cheyenne-r0919/Cheyenne/
7/3-21:59:42.906-[uniserve] Async Protocol FastCGI loaded
7/3-21:59:42.936-[conf-parser] Loading extension: mod-internal
7/3-21:59:42.940-[conf-parser] Loading extension: mod-extapp
7/3-21:59:42.943-[conf-parser] Loading extension: mod-static
7/3-21:59:42.948-[conf-parser] Loading extension: mod-action
7/3-21:59:42.952-[conf-parser] Loading extension: mod-fastcgi
7/3-21:59:42.955-[conf-parser] Loading extension: mod-rsp
7/3-21:59:42.960-[conf-parser] Loading extension: mod-ssi
7/3-21:59:42.963-[conf-parser] Loading extension: mod-alias
7/3-21:59:42.972-[uniserve] Starting RConsole...

7/3-21:59:43.003-## Error in [uniserve] : Cannot open server RConsole 
on port 9801 !
7/3-21:59:43.006-[uniserve] Starting Logger...

7/3-21:59:43.009-## Error in [uniserve] : Cannot open server Logger 
on port 9802 !
7/3-21:59:43.012-[uniserve] Starting HTTPd...
7/3-21:59:43.016-[uniserve] Starting task-master...

7/3-21:59:43.019-## Error in [uniserve] : Cannot open server task-master 
on port 9799 !

I should document better session/start in RSP API doc.

Has anyone tried to use things like Google API etc. from inside a 
RSP page?

DEBUG: Can I enable it via a RSP API call or a flag for just a specific 
RSP file?

You can find a short doc for Cheyenne's mods API in %Cheyenne/docs/developer-guide.html.

a way for a service to be asked permission to allow connection from 
the uniserve POV.

something like on-allow-connection? within the service api.

In fact the UniServe's API is the low-level API. Cheyenne is implemented 
as a Uniserve's service (httpd) and exposes it's own higher level 
API for mods.

In Cheyenne source package, you'll find an incomplete mods API documentation 
(Cheyenne/docs/developer-guide.html).

Not sure what you're trying to do, but, you shouldn't need to lost 
time of low level async stuff. UniServe is meant to offer a complete 
client and server API that should save you from working on low level 
stuff (unless what you're trying to do is not supported by UniServe's 
API).

It was very close (same API) to what Carl did for R3 (I think he 
just cleanup the code from that old alpha version).

That's very interesting and inspiring work. It's close to my own 
thoughts about a web app testing framework. You're very right, the 
main target should be the webapp API, not the UI. That's why I didn't 
invest in Selenium, I don't want to update scripts every time I change 
the UI without changing features.

Robert, see RESPONSE/FORWARD in the RSP API Reference page.

Having the TCP/IP part open-sourced in R3 will be great. It will 
allow to use much faster OS hooks for file transfers, extend the 
port! API to bind only on selected interfaces, etc...I wonder if 
the main event loop will be there also, so we can replace the not-scalable 
Select( ) call by other faster ones or even integrate libevent. That 
would definitely make Cheyenne able to handle a much higher number 
of connections.

Response/redirect: run Cheyenne in verbose mode using -vvv command 
line switch, to see what's wrong. You've probably passed a bad URL 
(see RSP API doc for examples).

I'm adding words which are commands within remarks' module using 
the do variant of config definition...  this allows me to grow a 
config by calling the same command multiple times.... this would 
be very unweildy to implement any other way (but not impossible)...


maybe a function-based api could allow us to "hook" into the GUI 
but its pretty hard to cover all possibilities in any case... anhow... 
back to modulating remark.

Doc, RSP by itself.. I use a version which does set word capturing 
(do you do that?) and allows page inclusion and context injection 
with "captured" words on the subpage. Do you do that?


Otherwise, a lot of Qtask "the application"  is Javascript on the 
UI calling API services - RSP is of little use there. The main web 
site... I would actually oppose REBOL. Why spend time there on e.g. 
a shopping cart when you can take one of the shelf and spend that 
time improving the real product (the service/application)?

So, RSP is good enough, except we are more API oriented with a Javascript 
front end :-)

The resource url would have to be saved by the cheyenne api .. a 
web app can't save it.