On Sat, Nov 27, 2010 at 11:17 PM, Mike Blumenkrantz <mike@...> wrote:
> On Sat, 27 Nov 2010 10:39:15 +0100
> Cedric BAIL <cedric.bail@...> wrote:
>> On Sat, Nov 27, 2010 at 8:08 AM, Mike Blumenkrantz <mike@...> wrote:
>> > Since you're afk in irc, I figured I would move this to the ml in case
>> > someone else ever wanted to know as well.
>> Ha, ha, ha ! You don't expect anyone else than me to answer those
>> existential questions ! I think you are right probably no one else
>> than me does use this API.
>> > 1) There are no docs for eet_node:
>> > http://docs.enlightenment.org/auto/eet/group__Eet__Node__Group.html
>> > This should probably be fixed at some point since the code is pretty
>> > annoying to read.
>> > 2) The reason I am not able to use eet for data serialization is because it
>> > lacks a suitable binary data member in Eet_Node_Data. In order to use
>> > binary data, you must have a function like this:
>> > Eet_Node *eet_node_binary_new(const char *name, void *data, int size)
>> > Otherwise you have no way of correctly using the node data once it has been
>> > retrieved. If I'm missing something, let me know.
>> Eet never provided such facility as a binary blob. Are you really sure
>> you want to send binary blob ? What kind of data are sending with it ?
>> I am asking because, we always avoided to put non typed data in eet,
>> so before starting adding this feature, need more information and
>> > 3) I am assuming that the most efficient way to use eet as I need would be
>> > to serialize using eet_data_node_write_cipher (with NULL for cipher), then
>> > simply read back eet keys on the other end using a data descriptor to go
>> > right to the struct? I'm purposefully avoiding using eet_connection since
>> > I have no need to use partial eet data structures; when using http
>> > transfers you must send the content length anyway (w3c standard), so I do
>> > my own internal buffering and can use the data once it has been fully
>> > received.
>> Use eet_data_node_encode_cipher, that would give you an allocated
>> buffer in memory that you can send as you want. So no need for any
>> Eet_File when you are transmitting data to another computer.
> Do you have any example code using this? The more I try to figure out how to
> make it work, the more that it seems to be impossible.
That's the only code I know that using the eet node API.