El dom., 17 may. 2020 a las 9:53, swizz one (<[email protected]>) escribió:

> Use this one, that one has an error. I would be grateful if you can critic
> my code if you have time, I am new to programming and I would like to learn
> and improve.
>
> El dom., 17 may. 2020 a las 9:30, swizz one (<[email protected]>)
> escribió:
>
>>
>>
>> El dom., 17 may. 2020 a las 9:26, swizz one (<[email protected]>)
>> escribió:
>>
>>> I did a user to user information exchange using webrtc(lindatchannel
>>> library).
>>> It is a rough implementation but it works although being new to codif,
>>> it might not be the best code written.
>>> I can sensld it to tou
>>>
>>> On Sun, May 17, 2020, 09:15 Sutou Kouhei <[email protected]> wrote:
>>>
>>>> Hi,
>>>>
>>>> I only re-implemented server implementation with recommended
>>>> API:
>>>>   https://gitlab.com/ktou/apache-arrow-glib-socket
>>>>
>>>> I'll do it for client implementation later.
>>>>
>>>> > Also, lets say I want to read the gconstpointer from another process
>>>> in a
>>>> > different language, all I would have to do would be storw do a byte to
>>>> > buffer transformation right?
>>>>
>>>> Right.
>>>>
>>>>
>>>> Thanks,
>>>> --
>>>> kou
>>>>
>>>> In <cackq_v17ohnqbzwobjiunuy1hk8ythdsitjsmzo+-phc-72...@mail.gmail.com>
>>>>   "Re: Builder.resize in c" on Wed, 6 May 2020 23:58:53 +0200,
>>>>   swizz one <[email protected]> wrote:
>>>>
>>>> > This is the example i did, the idea would be to have one thread
>>>> creating
>>>> > data and filling up the array, when full another thread sends it via
>>>> > websocket.
>>>> > The example just creats the buffer and sends it.
>>>> >
>>>> > Also, lets say I want to read the gconstpointer from another process
>>>> in a
>>>> > different language, all I would have to do would be storw do a byte to
>>>> > buffer transformation right?
>>>> >
>>>> > Your's Faithfully,
>>>> > Stevedan Ogochukwu Omodolor
>>>> >
>>>> > On Wed, May 6, 2020, 23:35 Sutou Kouhei <[email protected]> wrote:
>>>> >
>>>> >> Hi,
>>>> >>
>>>> >> > To prevent from allocating memory every time I have to append
>>>> value which
>>>> >> > in real time process it slow down because the computer jas to find
>>>> memory
>>>> >> > location everytime.
>>>> >>
>>>> >> Could you show your code? It seems that resize() isn't a
>>>> >> good use case for it.
>>>> >>
>>>> >> > Another question, the gconstpointer is the buffer of bytes righy?
>>>> >>
>>>> >> Right. gconstpointer is a typedef of "const void *":
>>>> >>
>>>> >>
>>>> >>
>>>> https://developer.gnome.org/glib/stable/glib-Basic-Types.html#gconstpointer
>>>> >>
>>>> >> Thanks,
>>>> >> --
>>>> >> kou
>>>> >>
>>>> >> In <CACKQ_V2=
>>>> [email protected]>
>>>> >>   "Re: Builder.resize in c" on Wed, 6 May 2020 23:11:32 +0200,
>>>> >>   swizz one <[email protected]> wrote:
>>>> >>
>>>> >> > To prevent from allocating memory every time I have to append
>>>> value which
>>>> >> > in real time process it slow down because the computer jas to find
>>>> memory
>>>> >> > location everytime.
>>>> >> > Another question, the gconstpointer is the buffer of bytes righy?
>>>> >> > Thank you very much.
>>>> >> >
>>>> >> > On Wed, May 6, 2020, 23:00 Sutou Kouhei <[email protected]>
>>>> wrote:
>>>> >> >
>>>> >> >> Hi,
>>>> >> >>
>>>> >> >> In <
>>>> cackq_v0cfs5q9jnjfo-ng1zeznc2hgavqdtyoj8rqrndzbg...@mail.gmail.com>
>>>> >> >>   "Builder.resize in c" on Wed, 6 May 2020 08:53:50 +0200,
>>>> >> >>   swizz one <[email protected]> wrote:
>>>> >> >>
>>>> >> >> > Is there an api similar to builder.resize in c to fix builder
>>>> length?
>>>> >> >>
>>>> >> >> "build.resize" mentions arrow::ArrayBuilder::Resize() in
>>>> >> >> C++, right? Could you stop abbreviating words as much as
>>>> >> >> possible to avoid misunderstandings?
>>>> >> >>
>>>> >> >> We don't have a C binding of arrow::ArrayBuilder::Resize()
>>>> >> >> yet. I'll add it later but could you show your use case? Why
>>>> >> >> do you need to fix builder length?
>>>> >> >>
>>>> >> >>
>>>> >> >> Thanks,
>>>> >> >> --
>>>> >> >> kou
>>>> >> >>
>>>> >>
>>>>
>>>

<<attachment: arrow_peer_to_peer_new.zip>>

Reply via email to