Re: Binary OGDL spec

[Patrick Doane]

Two comments on this:

  - It might be nice to support "random access" of the file.  This could
be implemented by including more size information.  For example, each
node could contain an offset to the the next sibling and the next child.

  - What is the reason for distinguishing between text-node and
binary-node?  Is it to save space by not including length data?

Rolf Veen wrote:

> Hi, all.
>
> I've uploaded a new spec of a binary version of
> OGDL, and an associated 'Remote functions' spec.
>
> The binary format is intended to be exchanged
> between machines, as it allows to intermix normal
> text nodes with images, etc.
>
> The RF spec defines a way to expose functions as
> remote services, by making the call and the response
> be OGDL binary objects.
>
>
> --
> Rolf.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Ogdl-core mailing list
> Ogdl-core@...
> https://lists.sourceforge.net/lists/listinfo/ogdl-core

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Ogdl-core mailing list
Ogdl-core@...
https://lists.sourceforge.net/lists/listinfo/ogdl-core

[Rolf Veen-2]

Patrick Doane wrote:
> Two comments on this:
>
>  - It might be nice to support "random access" of the file.  This could
> be implemented by including more size information.  For example, each
> node could contain an offset to the the next sibling and the next child.

The binary version is intended as a file format as well as a message
protocol, and this would add complexity at the emitter side and
also add quite an amount of extra bytes. I'm thinking for example in
using it to exchange information between a small device (a measuring
instrument, an inductrial device, etc) and a host, through USB, CAN or
whatever.

>  - What is the reason for distinguishing between text-node and
> binary-node?  Is it to save space by not including length data?

We need to identify text nodes without extra (external) type or
schema information because they are used to name other nodes.
We would not be able to do much with only untypified binary nodes.
Normal OGDL is pure text, its seems natural if binary OGDL is a
superset of that.

--
Rolf.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Ogdl-core mailing list
Ogdl-core@...
https://lists.sourceforge.net/lists/listinfo/ogdl-core