Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

Rugby 4: release and documentation!

 [1/3] from: m::koopmans2::chello::nl at: 15-Aug-2001 13:59

Hi List, Rugby 4 has been released to the Reb as rugby4.r You can find a distribution and documentation on: Many thanks to Allen Kamp for web hosting and for Ernie van der Meer for co-coding. Rugby is a rebol request broker that simplifies distributed computing dramatically. What's new? - poll-for-result has been dropped and changed to result-available? and get-result. See the docs for usage. Rationale was that you couldn't distinguish between false values when using poll-for-result. - The serialization mechanism has been greatly enhanced and works much better. - sexec also supports the /oneway and /deferred refinements - Rugby servers generate stub code that can be automatically imported by clients using get-rugby-service <url> This provides wrapper functions for all rugby service functions available on <url> to the local machine. Effectively you don't need to type rexec [ echo "lala" ] but you can just do echo "lala" which handles everything transparently. See the docs. Very very very cool. Thanks to Ernie! - Added the source of Rugby in modules with a built system in the main distrib. For those who want to add/change. - Added documentation (The Rebol Zine article updated for this release) Enjoy and let me know what you think. --Maarten

 [2/3] from: koopmans:itr:ing:nl at: 15-Aug-2001 15:16

Forgot to mention: you can now use urls as well in stead of port specs when using (secure-)serve sexec and rexec. --Maarten

 [3/3] from: brett:codeconscious at: 16-Aug-2001 0:56

> Enjoy and let me know what you think.
Great work! I particularly like the proxy idea. It makes distributed computing almost too easy. Looking forward to the applications Rugby inspires. Already I'm starting to think of my very own personal application server that "exports" lightweight View GUIs that are automatically connected back to their applications via Rugby. The possbilities are endless. Even without an app server, I'm wondering whether the single machine only application is finally dead. Why leave an application running on one machine only when using your code makes it is so easy to partition the application's functions across multiple machines - even for personal use?... Hm.. Now, any thoughts on a distributed versioning (update) management system? Don't want my wife overwriting my Rebodex name changes.... Thanks again for a great script! Brett.