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

[REBOL] Re: IOS (was: Browser gripe)

From: jason:cunliffe:verizon at: 17-Mar-2002 22:53

Hi Gregg Thanks. Yes your description helps. I just went to check on and delighted to discover they have a new links to IOS articles and last some new press coverage. Spring must be here :-) Funny RT didn't post an announce to the list, or did I miss something?
> I can publish things via IOS to a server. I can then go anywhere in the > world and fire up the IOS/Link client on a clean machine, and everything > I've published (or that anyone else has published on the server) is > automatically sync'd. Now, lots of people on this list will undoubtedly > think "Yeah, so what. I know of n other systems that do that too." The
> that makes IOS great, to me, is how simply, easily, and reliably it all > works.
ok: A. synchronize distributed data easily That something we all want the smallest possible headache to do? Please can you clarify what "firing up" IOS/Link client on a clean machine involves. What is the cost per link client? How easy to customize the look of the client?
> IOS doesn't provide everything you might ever want, but it's easy to
> For one project I'm working on, we're using a remote Rugby server along
> IOS to provide facilities that I don't yet know how to provide via IOS.
> I built the original app under /View, we installed IOS, published the > scripts, and it ran under IOS without any changes. IOS becomes a simple > deployment mechanism. I can have the Conference reblet fired up, and have > people looking at the app. As they make suggestions, I can tweak it on the > fly, re-publish it, and they can run it again to see the changes. If I
> to roll back to a previous version, IOS maintains a history of published > versions for me automatically.
You mean you are tweaking your own /View scripts which are now distributed and synchonrized [published] via IOS ? The history function sounds nice, like the cool 'versions' thing in Zope. Is 'publish' on a demand-basis? If clients are on-line 24/7 like DSL how quickly are updates propagated? Is this architecture like DNS? Does IOS care what your Viewlets are? Can non-Rebol/Link clients also access them [in non published mode] ? Where is this stuff explained? Are there docs? cheers ./Jason