World: r3wp

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"

however... is there a simple way to change the mime-type of the on-response 
fuction "on the fly" 

the default on-response function is set to "text'/html" when is this 
fired?

(embed module)

Do i need to catch this and inject into the on-response function 
before processing the post data etc?

Ok.. this seems to work.. kinda.. 

	on-response: func [req params svc][	

  ;-- this callback is useful to mutualize the HTTP response settings.
		
		thetarget: copy req/in/target
		print join "target: " thetarget
			either found? find thetarget "." [
			mimetype: parse thetarget "."
			
			if (last mimetype) = "swf"[
			print "is a flash file"
				req/out/code: 200

    h-store req/out/headers 'Content-Type "application/x-shockwave-flash"
				]
			][
		print "is text/html" 
		req/out/code: 200
		h-store req/out/headers 'Content-Type "text/html"
		]
	]

The flash movie is getting to the page with the proper mime-type 
and <object> tag.. but it's not firing? 
Im reading the flash movie using  read/binary  ??

I guess they don't call it "the bleeding edge" for nothing.

Ok.. reading binary doesn't seem to work with .swf