Yes you agree. Maybe that general format could create some problems when one try to exchange data from Rebol (e.g.: client application) and a server (e.g.: java, php, etc...).
Actually, I'm creating a client rebol over a server Java (Jboss). I partially solved the problem about datya exchange in this way: java-server creates formats for rebol, and rebol send data to server (java) creating xml. It works, but it is not really the best solution (not much elegant, a little bit confusing for maintenance, etc....). --Alessandro On 4/19/06, Jeff Massung <[EMAIL PROTECTED]> wrote: > I haven't followed this thread in its entirety. However, why not just use > REBOL as the data carrier? Is there any particular reason to use XML (whi= ch > is an absolutely terrible data format, but I digress) or YAML? Why write = an > INI parser in REBOL instead of just loading up data that looks like this: > > bob: [EMAIL PROTECTED] > jane: [EMAIL PROTECTED] > > The only reason to not use REBOL would be if you are dealing with an > existing format, or dealing with a format that needs to be shared across > different programs (of which some are not REBOL). > > Jeff M. > > -- > [EMAIL PROTECTED] > > -- > To unsubscribe from the list, just send an email to > lists at rebol.com with unsubscribe as the subject. > > -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
