@Cesar
I've made a little advancement on dynamic encoding/decoding, here's a gist
with a proof of concept: https://gist.github.com/ifesdjeen/7902409
On Wed, Dec 4, 2013 at 8:28 AM, Cesar Canassa wrote:
> Hi,
>
> I see that the repeated-type requires a constant repeat count. Are you
> planning t
I've added a missing option for wrapped buffers:
https://github.com/clojurewerkz/buffy#buffer-types
On Wed, Dec 4, 2013 at 9:28 AM, Ulises wrote:
> While we're on the subject, I found no way of decoding/interpreting an
> already existing sequence (ByteBuffer) of bytes, but only one that had
> b
I've added 32-bits based bit type to Buffy:
https://github.com/clojurewerkz/buffy#bit-type
Does it suit your needs? If not, what length of bits do you require?
On Wed, Dec 4, 2013 at 3:58 PM, Rob Day wrote:
> On 29 November 2013 22:15, Alex P wrote:
> > Buffy [1] is a Clojure library to work
@Thomas, let me know if you run into any problems. Since the project is
quite young, I'm very open to add a couple of features. Rob, Ulisses and
Cesar have done a very nice job providing some very nice ideas!
On Sat, Dec 7, 2013 at 12:05 AM, Oleksandr Petrov <
oleksandr.pet...@gmail.com> wrote:
@Rob
I have a working prototype of bits, which are encoded from 32 flags and
decoded back to them. I've added a couple of helper methods such as
`set-bits-at` and `get-set-bits` and so on to facilitate it.
Although I recommend using enums for that (which is possible in majority of
cases).
I'll rele
On 29 November 2013 22:15, Alex P wrote:
> Buffy [1] is a Clojure library to work with Binary Data, write complete
> binary protocol implementations
> in clojure, store your complex data structures in an off-heap chache, read
> binary files and do
> everything you would usually do `ByteBuffer`.
I
Thank you Alex,
I have been paying around with Gloss for a while now and realised it is not
quite suitable for the protocol I am trying to en/decode. I'll give Buffy a
try and see whether it is a better fit for my problem domain.
Thanks again,
Thomas
On Monday, December 2, 2013 9:09:48 PM UTC
While we're on the subject, I found no way of decoding/interpreting an
already existing sequence (ByteBuffer) of bytes, but only one that had
been created with compose-buff. Am I missing something?
On 4 December 2013 07:28, Cesar Canassa wrote:
> Hi,
>
> I see that the repeated-type requires a co
Hi,
I see that the repeated-type requires a constant repeat count. Are you
planning to include a more dynamic version à la Gloss prefixes/headers?
The lib looks really nice. Binary handling libraries are really helpful.
Thanks,
Cesar Canassa
On Mon, Dec 2, 2013 at 7:09 PM, Alex P wrote:
> I
It's different in a way we manipulate the data:
We've opted out for default-lazy way (you're getting and setting separate
values instead of serialising/deserialising an entire payload).
Another difference is that we don't have Lamina as a loaded artifact (which
may not be an issue for majority
Looks really really great and could you please explain how it differs from
gloss [1]. Any advantages? Disadvantages?
Thanks
Thomas
[1] https://github.com/ztellman/gloss
On Friday, November 29, 2013 10:15:45 PM UTC, Alex P wrote:
>
> Buffy [1] is a Clojure library to work with Binary Data, write
Good work! Thanks!
2013/11/29 Alex P
> Buffy [1] is a Clojure library to work with Binary Data, write complete
> binary protocol implementations
> in clojure, store your complex data structures in an off-heap chache, read
> binary files and do
> everything you would usually do `ByteBuffer`.
>
>
Buffy [1] is a Clojure library to work with Binary Data, write complete
binary protocol implementations
in clojure, store your complex data structures in an off-heap chache, read
binary files and do
everything you would usually do `ByteBuffer`.
Main features & motivation to write it
* partial
13 matches
Mail list logo
