World: r3wp

Developers stopping their work on R2 waiting for R3 are just loosing 
time. I bet that R2 will still be the stable REBOL in 6 months (maybe 
even more). For professional work, stick to R2, until R3 reaches 
a stable level.

wrong group

is the new version contain any bug fixes or is it justs control panel 
enhancements?

Hi Graham, never tested Cheyenne with ODBC. Do you see differences 
between encapped version and source version running on rebcmd.exe 
?

Yes.

Bugfixes and new features. Control panel is not ready for prime time.

I encapped Cheyenne to run my patient portal and the data returned 
from a sql query is all corrupted

did you try to : probe copy db ? (and see the raw result returned 
by the db port)

I am wondering if anyone can reproduce this .. or whether it's just 
me!

No.  I wasn't sure where to begin to debug this.

and I had a deadline to meet .. so I just used the source code version

are you using the 'do-sql command ?

yes

are you on XP or Vista ?

2003

Haven't tested under XP or Vista yet.

'do-sql is using a trick to determine if the scheme is using a native 
driver (RT's) or a user-defined one. It's testing db-port/handler 
: none means native driver, other value means user-defined. This 
was working ok with the native MySQL driver, could you tell me if 
this test is also ok for a odbc:// driver ? (just open an odbc connection 
in console mode and tell me the value of db-port/handler)

Hey Doc, welcome back.

Hi Terry, back for 5 min only, I was on the road to bed ;-)

Can I just drop the embed module into the latest Cheynne to make 
it work?

Yes, it should work (IIRC, you have to comment all other modules, 
see the doc in the embed-demo.r sample).

mod-embed.r

Ok.. cool.

It's working great by the way.

If you have 3 minutes left, can you explain the shared space between 
cheyenne and uniserve please.

Which one ? uniserve/shared ?

Uniserve is just the underlying network layer for Cheyenne.

You once mentioned the need to use the 'shared' something or other 
for communication between uniserve modules and cheyenne.

It also provides the IPC support.

International Political Corruption?

If only...I would be a rich man ;-). Inter Process Communication

:)

Actually, i have a response from a web page pushing data to a uniserve 
service.. so kinda close.. just wondering if there's a preferred 
method.

One last thing.. how do you feel about incorporating cheyenne into 
a GPL product?

Does the uniserve service share the same REBOL VM than Cheyenne (or 
are they running on 2 different processes ?)

It was two, then I dropped the other and it worked .. woohoo.

Cheyenne is BSD, don't know how it can fit in a GPL product, but 
I guess there's no problem doing that (at least for me).

Ill take that last sentence as your license ;)

Check out my natural language URLs if you get a chance.. in the Atom 
chat group... running on Cheyenne

;-) Sure, I'll try it.

>> p: open odbc://remr
>> db-port: first p
>> probe db-port/handler
none
== none
>>

thanks, so that's not the cause of the issue. You need to probe or 
log the raw output of the following snip of code in %handlers/RSP.r 
('do-sql function) :

any [
	insert port data
	copy port
]

Ok.  I'll try that tonight.

Working at present :(

If the output is ok, it's an issue with Cheyenne, else, it's an issue 
with encapped odbc.

Going to sleep, will be back this weekend.

Thanks Doc

Nenad, how do I set the mime type for delivering up a Flash binary?

er.. ok.. found it.. h-store req/out/headers 'Content-Type "text/html"