World: r3wp

What is the reason to do R2 release in current time-frame, when we 
are supposed to be heading for R3 beta?

Ok, on ODBC.

Encryption ports ...

Pekr, promises made.

DLL access?

Pekr, because R3's compatibility policy depends on continued support 
of R2.

Terry - DLL and Shell were released long time ago.

Believe me, I do not want to take extra time away from R3 beta, but 
also, I did not want to delay R2 this long.

Yes ..

The only thing left in /Command is - fastcgi, SSL, ODBC, mySQL?

so, just release a license ??

And Oracle (does anyone use that?)

if SSL and ODBC would be released for free, it would make many folks 
happy ...

Larry Ellison?

B: on O, yes. Odd as it seems.

simplest thing to do is just release a license ...

BrianH, Carl ... under Windows, many DBs are just used via ODBC drivers 
...

Graham, let's do it right.

Of course, you could make some real headlines, and just BSD the whole 
thing.

BrianH ..doing it right might mean a wait for a long time

Carl was also suggesting releasing a license to IOS ....

No it won't take long - it's just a matter of removing the license 
code and doing a rebuild.

please, fix this 300ms delay !
  timer [call/wait "echo 1"]
1
;   0:00:00.301731
  timer [call/wait "echo 1"]
1
;   0:00:00.301543

And if it does take long, we can do it right next month and do your 
approach now.

W: in windows or Linux?

os x but geomol ryoed on linux I think a swell

ryoed -> tryied

there might be a reason why there was such delay put into REBOL?

W: I've posted the C source to Call a few times, but no one has ever 
offered any fixes.

yes i think so

Well, it is quite possible that fixes got lost-in-reply.

BrianH please? 8-)

People need to nag me more if they contribute a fix, and it gets 
lost.

BrianH .. a public license means that everyone gets ssl, odbc, oracle, 
encryption today without waiting for a new build.

I don't know though if such a license would also be usable for the 
SDK ... which Carl may not want to do .

P: there is no reason for such a delay.  But, then, the code is not 
at all simple. If you've ever seen it, you would vomit. (PS: I did 
not write it.)

:-) I do remember - over 1200 lines of code ... but at least "it 
works", and in R3 'call is almost unusable ...

300 ms is a lot of time in response time when using call/wait or 
call/output in a Cheyenne rsp. Please fix it!

So, BrianH, have you summarized the priorities in r2-beta yet ?  
:)

Is RAMBO still active? Many bugs probably there. I wonder if over 
the time (depends on how long we want to continue to maintain R2 
family of products) we should port it to CureCode?

Will, that "echo" calls a cmd.exe internal command on Windows. Might 
that be part of the delay?

I agree with Graham - R2 is so wide field, that we should move the 
project to R2-beta world, which is already well established ...

Give me a little time to go over them, I should have a list by this 
evening. I'm at work today.

timer [call/wait "print 1"]
1
;   0:00:00.301498

>> timer [call/wait "print 1"]
0:00:00.031

>> t1: now/precise call/wait "print 1" t2: now/precise print difference 
t2 t1
0:00:00.082

Using R2Beta should be fine for this week, but we need to switch 
over to using the R3 development infrastructure before the release 
next month. We won't have the time and effort available for monthly 
releases if we can't share resources. The rapid releases of R3 are 
only possible because of the R3 development infrastructure.

humm.. than the beahaviour is on nix only

release this week ....

is point #1