AltME groups: search

Like Kaj request for returning the last element.

That's through Cheyenne's CGI mode, so with standard input reading, 
it should also be able to handle a POST request

My thoughts are as follows - if we request some small fixes, which 
can be workarounded, then let's spend RT's development in R3 area. 
Fix hard crashes and that's it for 2.7 release ...

Have any of you ever seen where the request-date requester does not 
display the correct month? For example, it will say May 2009 when 
it is actually displaying June 2009. Selecting a date will give you 
the june date. Using the /date refinement doesn't seem to help either.

Post the request on CureCode once we have a R2 project for it.

Steeve... that's an interesting request.... what's it used for?

like this?
the cli connector is using the cli component nearly all major
databases delivering. the connection is made via rebols 

call/wait/info/output/error and a simple parse after, for the resultset.
I am using this prototype mainly for a q & d connect

to mysql/postgresql/monetdb/sqlite. on my list are also connectors 
for

firebird/oracle/greenplum/sybase/ingres/infobright/frontbase and 
cassandra.
pros:

1. very fast for single requests
2. no rewrite of code needed if a new version or protocol is out
3. easy 'data migration' between the db's

4. adding new db's are a matter of hours only (see the cli spec thats 
all)
5. fast prototyping and testing for new db's

6. robust, never had any trouble with cli's even with bigger resultsets

7. should be perfect also for traditional cgi (the process starting 
overhead is minimal, execpt you name is facebook)

8. very small footprint (~120 lines for connecting to 4 db's, could 
be the half)

with a nice tcp-server component like rebservice the 
cli multi connector could be very usefull as a c/s connector.
I made a test with 2.000 concurrent calls (simple select) 
on a 4 gig quadcore. the cpu was only close to 50%, a good value.

cons:


1. slow if you have very much serial inserts (unless you shape them 
into one sql query)
2. need to start a cli process for every request
3. needs a tcp server for non-local connections
4. some more, but who cares ;-)

with a solution to keep the cli open from rebservice,

these cons could disappear and the speed diff overhead to a memory 
based lib
could be marginal.

there are 3 extension which would be very cool. 

1. tcp server for easy remote request  without the need for the cli 
on the client side (e.g. rebservice)  

2. a smart sql-syntax mapper for interactive migration (you can't 
read e.g. a mysql dump directly into postgresql) 

3. a stable cli alive holder to eliminate the startup payload for 
the request.

Just posted a ticket about this for R3 (by request). This shows the 
problem:
>> http://user%40rebol.com:[blah-:-www-:-rebol-:-com]/
== http://[user-:-rebol-:-com]:[blah-:-www-:-rebol-:-com]/
; should be http://user%40rebol.com:[blah-:-www-:-rebol-:-com]/

What is the plan for next release ?
Do we need to post bug/request on RAMBO ?

one indicator: IE 8 (which is not my default now since I moved to 
K-mleon) runs VIEW 2.7.8 as a right-click option using RUN - but 
download with IE8 and run from Explorer file view correctly triggers 
a request to authorize due to no "valid" digital signature for MS 
- yet this MS alert fails to trigger when run after download using 
K-meleon browser (yet no issue after K-meleon downloads CORE 2.7.8 
)

The request-to-authorize thing is managed by an extended attribute 
in one of the other forks of the file on NTFS, and not on FAT. Have 
you tried Chrome or Firefox?

No, not a musical request program, just whole REBOL ecosystem being 
 a hilarious parody ....

The Request Pipeline

I put in a request for Ladislav's feedback in a ticket comment, and 
in other AltME worlds where he works. Including the RMA world, where 
they write code that would be affected by this.

Doc, do you see something ? 
I pulled a request.

Your pull request disappeared, I guess you'll publish a new one.

I repulled a request.

It seems a ticket is opened for each pull request...

This article was an influence in the decision to request people to 
register to the Google Group - http://ejohn.org/blog/google-groups-is-dead/

I'll  guess that  the next request will be for an unsigned integer.

I've taken over Andreas' changes, corrected the runtime syscall, 
and uploaded new empty, hello, reply-server and request-client

I am considering your request for an implicit casting for imported 
functions using a return: [logic!] declaration. I could add it, by 
forcing a type conversion if the function is imported, but if the 
function already returns the right value (0 | 1), it will have to 
pay an extra cost for a useless conversion and no way to avoid it.

unless all [
	(
		message: receive socket 0
		as-logic message
	)(

  prin "Received request: "  print as-c-string message-data message
		end-message message
	)(
		;wait 1
		send socket  as [byte-ptr!] reply  1 + length? text  0
	)
][
	print zmq-form-error system-error
]

Btw, your code snippet could be rewritten as:

message: receive socket 0
unless all [
	as-logic message
	end-message message
	;wait 1
	send socket  as [byte-ptr!] reply  1 + length? text  0
][

 prin "Received request: "  print as-c-string message-data message
	print zmq-form-error system-error
]

Cross-posting jocko's reply from RebelBB french forum: 

There are two steps in this DLL: 


- first send a request to the Google api, for instance : http://translate.google.com/translate_tts?tl=en&q=hello+world
Google returns an audio file : translate_tts.mp3


- second, automatically open this file and play it. I use a DirectXShow 
filter (windows only), directly able to render the url. In the case 
of Linux, cUrl could do the first step, and, for instance VLC the 
second

Doc, the 0MQ binding still works, so you can use the request/reply 
example, on Linux or Windows

done.. you can find complete diff for the pull request here: https://github.com/dockimbel/Red/pull/201/files

Code review of your pull request finished. Only minor things except 
maybe for the addition in `get-variable-spec` that might cause some 
issues.

Pull request #201: Oldes, thank you very much for your changes. It 
should be ok now for merging, I will just run a few more tests before 
that.

No, not anything, but what normal consument expects. There is plenty 
of bare bones DVD players, DVB-T tuners, and apart from video, all 
handle even photos, as I think, that in the age of digital cameras, 
it is pretty normal to request such a feature. But - whatever ...

bash-4.0# ./request-client 
0MQ version: 2.1.4

Connecting to Hello World server...
Sending request 1
Received reply 1: World
Resource temporarily unavailable
Sending request 2
Received reply 2: World
Resource temporarily unavailable
Sending request 3
Received reply 3: World
Resource temporarily unavailable
Sending request 4
Received reply 4: World
Resource temporarily unavailable
Sending request 5
Received reply 5: World
Resource temporarily unavailable
Sending request 6
Received reply 6: World
Resource temporarily unavailable
Sending request 7
Received reply 7: World
Resource temporarily unavailable
Sending request 8
Received reply 8: World
Resource temporarily unavailable
Sending request 9
Received reply 9: World
Resource temporarily unavailable
Sending request 10
Received reply 10: World
Resource temporarily unavailable
Resource temporarily unavailable
Resource temporarily unavailable

Here is the fix in the pull request: https://github.com/dockimbel/Red/pull/206/files

Yes I do some variant of that too. Hm.. maybe I just viewed all this 
wrong so far.. I imagined that when something will go wrong I will 
be looking and hacking on generated javascript (I use it and console 
sometimes), but yes I should view it that I will be changing the 
topaz with print statements for example and viewing the output.


In this case .. is it planned so that topaz could be automatically 
compiled on http request (in dev mode at least)? so that you can 
just edit and reload, like with javascript (without manually compiling)?

Nenad uses Github issues for bug and feature request tracking for 
Red though perhaps the wiki would be better for a List of REBOL incompatabilities?