binary_to_term size limit

[Valentin]

Hello Heinrich,


I had a similar problem... well, about 2+ years ago with erl_interface
library -- it appears that this library is using fix-size buffer and that
can cause the problem you're referring to. However, as far as I can
remember, our C/C++ programs did crash & burn when we tried to push large
amount of data using a single send.

On the other hand, the new "ei" library doesn't seem to have the same
limitation regarding the size, but introduced few... say, considerations.
For example, if you are using ei_send, the term that you're sending must be
prefixed with version magic number.  This is not needed for ei_rpc, as the
function does it for you.

We wrote few C++ wrappers around ei library and never looked back -- it
works very well for us (although, I must say, we try to keep our C++, or
rather non-Erlang exposure to a bare minimum).

Valentin.

PS
It appears that you're based in South Africa? If so, give me a ring so we
can exchange experiences.
(+27 83 212 9180)






----- Original Message -----
From: "HEINRICH VENTER" <HEINRICH.VENTER@REDACTED>
To: <seb@REDACTED>
Cc: <erlang-questions@REDACTED>
Sent: Friday, July 18, 2003 9:15 AM
Subject: Re: binary_to_term size limit


> >The term must have gone stale, how did you transport it? :-)
> Stale?
> I used erl_interface.  The term is constructed in C code.  Perhaps
erl_encode has a size limmit for the term it can encode then?  I used
erl_term_len to allocate a buffer of the correct size, and the allocation
goes smoothly.
> Once the binary representation is recieved by erlang the binary_to_term
call fails.  It works for smaller terms, so logically somewhere along the
line a size limmit exists.  Perhaps the limmit is internal to erl_interface?
>
> Thanks
>
> -]-[einrich
>
>
############################################################################
#########
> The information contained in this message and or attachments is intended
> only for the person or entity to which it is addressed and may contain
> confidential and/or privileged material.  Any review, retransmission,
> dissemination or other use of, or taking of any action in reliance upon,
> this information by persons or entities other than the intended recipient
> is prohibited. If you received this in error, please contact the sender
and
> delete the material from any system and destroy or copies.
>
############################################################################
#########