World: r3wp
[Ann-Reply] Reply to Announce group
older newer | first last |
Kaj 5-Mar-2011 [2497] | Nice doc, Jocko |
JoshF 6-Mar-2011 [2498] | About disreb: Sorry to be unclear originally. At the moment, it's R2 only (I'm currently sticking with the latest version of R2 because I understand that it has a more stable GUI), however I am very willing to incorporate changes for R3. I'm not yet sure what the best fashion of collaboration with the Google code site is, but hopefully I'll have some time to investigate tomorrow. Sorry for the late reply, but I have imperfect access to AltMe (it's firewalled at work and I forgot my password (ha!) so I don't have it working on the computer I'm programming disreb with). @Oldes, I hope you find it useful should you chance to use it! Thanks! |
Robert 6-Mar-2011 [2499] | Andreas, is you 0MQ stuff synchron only? Or does it support async message passing via callbacks? |
Andreas 6-Mar-2011 [2500] | Robert, it can do both sync and async. But no callbacks, async is done using a WAIT-style (or select/epoll-style, if you prefer) approach, using zmq-poll. |
Robert 7-Mar-2011 [2501] | Just to be sure I understand: 0MQ makes async call however it does it, and between 0MQ and Rebol the async is that I have to poll from Rebol side to check if the call is already done? |
Janko 7-Mar-2011 [2502x2] | 0MQ binding.. that is awesome! Does/will this work for R2 also maybe? :) |
And big kudos for making the Redis library! | |
Andreas 7-Mar-2011 [2504x2] | Robert: you have two primitives send & recv. Both _block_ per default: send until there it manages to enqueue the message in an internal buffer, recv until it fully read a message. You call both functions with a NOBLOCK flag, in which case they won't block but return immediately, with an EAGAIN status code in case they did not manage to write/read anything. Finally, you also have a poll primitive, to which you pass a list of sockets you are interested in and an (optional) timeout. Poll returns you a list of sockets which are "active", i.e. which can be safely read from (or written to) without blocking. |
ddharing: The 200kmsgs/sec results are from a run on Linux. | |
Gregg 7-Mar-2011 [2506] | Very cool Andreas! Can't wait to play with the new examples. |
GrahamC 8-Mar-2011 [2507] | Andreas - let us know when you port LNS to run over zeromq :) |
Rebolek 17-Mar-2011 [2508] | Great work, Jocko! Any R3GUI problems or bugs you want us to fix? :) |
GrahamC 17-Mar-2011 [2509] | Why not leave panel and hpanel as synonyms, and group/hgroup ? |
Henrik 17-Mar-2011 [2510] | Moving to REBOL3 GUI... |
Gregg 19-Mar-2011 [2511] | Thanks to the RMA team for their progress posts and updates. |
Gregg 23-Mar-2011 [2512] | Very cool script Massimiliano! |
GrahamC 24-Mar-2011 [2513] | I clicked on the "Draw" button for the plotterdemo and nothing happens ?? |
DideC 4-Apr-2011 [2514x2] | MaxV: remind me a script I made 8 years ago : d http://membres.lycos.fr/didec/rebsite/whoswho/whoswho.r |
do http://membres.lycos.fr/didec/rebsite/whoswho/whoswho.r | |
MikeL 4-Apr-2011 [2516] | Didier.... Very nice. |
Andreas 24-Apr-2011 [2517] | Kaj, when cloning your fossil repository: fossil: *** time skew *** server is fast by 13.1 seconds |
Kaj 24-Apr-2011 [2518] | Odd, it doesn't warn me if the skew is within a few minutes or so. Anyway, it seem to be just a warning, and I wouldn't worry about 13 seconds |
Andreas 24-Apr-2011 [2519] | You might want to fix the system time on this machine. |
Kaj 24-Apr-2011 [2520] | 13 Seconds? I can live with that |
Andreas 24-Apr-2011 [2521x2] | 13 seconds today, half a minute next month, ... |
NTP not an option? | |
Kaj 24-Apr-2011 [2523x3] | Sure, and Fossil will nicely warn me when it gets significant, and then I'll adjust it |
NTP is on the roadmap for this server, but with low priority | |
Does Fossil issue a warning when you update? | |
Andreas 24-Apr-2011 [2526] | yes |
Kaj 24-Apr-2011 [2527x2] | Strange, not for me, and the time of my workstation is routinely off |
What system are you on? | |
Andreas 24-Apr-2011 [2529] | Why would that matter? |
Kaj 24-Apr-2011 [2530] | Because I can't replicate it |
Andreas 24-Apr-2011 [2531x2] | My systems are properly time-synced. |
Various Linuxes, fossil 047e06193b on all of them, all of them synced. | |
Kaj 24-Apr-2011 [2533] | Mine aren't, so that must be the solution :-) |
Andreas 24-Apr-2011 [2534] | The esperconsultancy httpd is ~14 seconds off. |
Kaj 24-Apr-2011 [2535x2] | That's much better than I expected :-) |
What's the date of your Fossil version? | |
Andreas 24-Apr-2011 [2537] | This is fossil version [047e06193b] 2011-04-13 12:05:18 UTC. |
Kaj 24-Apr-2011 [2538] | I'm on the previous version of a month before, so maybe that makes a difference |
Andreas 24-Apr-2011 [2539] | Not really. |
Kaj 24-Apr-2011 [2540] | You're reporting a difference, aren't you? |
Andreas 24-Apr-2011 [2541x2] | 2011-03-16 reports the same warning. |
The difference is most likely that my systems have a synced time, whereas your workstation has not. | |
Kaj 24-Apr-2011 [2543] | Yes, that's what I suggested |
Andreas 24-Apr-2011 [2544] | Exactly. The fossil version doesn't matter much. |
Kaj 24-Apr-2011 [2545] | So, I can't replicate your problem, and it doesn't prevent Fossil from functioning, does it? |
Andreas 24-Apr-2011 [2546] | You can easily replicate my problem: sync your system time properly. |
older newer | first last |