Mailing list home
  Find posts   Help

Latest messageRecent messages

Other threads:
 Prev: CGI, uploading file using HTTP, server sid
 Next: sorting a serie ....

 Random thread

Indexes:
 By topic
 By date
 By author
 By subject
Join the Mailing List....
AccessibilityAbout / FAQ
Member's loungeContact/FeedbackOther REBOL links
Membership:
member name

password

Remember?

Not a member? Please join
4-Jun 4:59 UTC
[0.087] 9.229k
Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

[Fwd: Re: Rugby bug-report]

 [1/3] from: Maarten::Koopmans::surfnet::nl at: 18-Jun-2003 10:05


FYI. Any testers on all kinds of windows/linux etc. appreciated. As are any ideas. --Maarten Hi Volker,
> rugby is fun :)
Thanks.
> But it has a mysterious interaction with 'launch, a test-script below. > > Also, when i return a 'word, it is executed in the client, instead of > returned as lit-word. > Is that intentional?
No, just something I never got to work. Should be in the "known limitations" section.
> REBOL [ > Title: "rugby hangs with launch"
<<quoted lines omitted: 33>>
> ;port: open/no-wait tcp://:8002 forever[wait reduce[port :0:0.2]] > ;Volker
OK, but this may be a REBOL/view problem 1.2.x with x>8. On what platform did you test? The "launc" interaction is strange, so is resetting the clock (to what?). Looks like an OS error/interaction. AFAIK you can't reset the clock in REBOL. Can you track it down more so we can file a bug report to RT? --Maarten

 [2/3] from: nitsch-lists:netcologne at: 18-Jun-2003 17:16


Maarten Koopmans wrote:
> OK, but this may be a REBOL/view problem 1.2.x with x>8. On what > platform did you test?
<<quoted lines omitted: 3>>
> so we can file a bug report to RT? > --Maarten
No, not "restart". Continues to run. When the launched scripts quits, the launcher stops handling events. No buttons react etc, timers stop etc. The clock is a demo to show if events are processed. But with an incomming connection the event-loop "restarts", clock continues running. I looked in the rugby-code and saw its basically like forever[wait reduce[port :0:0.2]] so i tried that with port: open/no-wait tcp://:8002 forever[wait reduce[port :0:0.2]] instead of serve[] No problems. Looking at the rugby-script it seems it does some tricky stuff with make port!, so i think its triggered by something in the initialisation. Its on Suse 8.0. -Volker

 [3/3] from: maarten:koopmans:surfnet:nl at: 18-Jun-2003 18:14


I'll have to look into it but that'll take some time as I'm *extremely* busy. As soon as I have something to test I'll let you know. --Maarten Volker Nitsch wrote:
Notes
  • Quoted lines have been omitted from some messages.
    View the message alone to see the lines that have been omitted