AltME: R3-GUI
Messages
Friday 21st June, 2013
Andreas
21:33
So no prot-http at all?
GrahamC
21:33
I'm not .. I'm using tcp
Cyphre
21:33
day=say
21:36
also this is a bit confusing:
>> probe make event! [type: 'read port: p]
make event! [
type: 'read
port: make port! [
spec: make object! [
title: "TCP Networking"
scheme: 'tcp
ref:
tcp://:8000
path: none
host: none
port-id: 8000
]
...
gob: make port! [
spec: make object! [
title: "TCP Networking"
scheme: 'tcp
ref:
tcp://:8000
path: none
host: none
port-id: 8000
]
...
offset: 0x0
]
Andreas
21:37
What's P?
Cyphre
21:37
why is the GOB fileld here? and why it is of port! value?
21:37
sorry,
p: open
tcp://:8000
21:38
(just something to test)
21:38
maybe it's just a bug of event! mold though
Andreas
21:38
I think that's because the gob & port fields share memory in an event.
Cyphre
21:39
yes, that's possible
GrahamC
21:39
as you can see
https://github.com/gchiu/RSOChat/blob/master/rsochat.r3#L199
my mini-http uses tcp port
Andreas
21:46
So yes, looks like a MOLD quirk.
Cyphre
21:47
GRaha, yes, so that proves the crash can be caused by plain TCP scheme. So we should somehow reduce the case to a minimal code which crashes R3...
21:47
=Graham
Andreas
21:47
R3GUI does not, by chance, generate READ events :) ?
GrahamC
21:49
It's not due to the timer code because I saw this bug before then
Cyphre
21:49
Andreas, fortunately no :)
Andreas
21:50
Well, fortunate for R3GUI, I guess :)
Cyphre
21:51
ah, sorry it's not READ but CONNECT event!
21:51
Andreas, yes :)
Last message posted 270 weeks ago.