MaG21
commented
7 years ago Hello,
first, thanks for taking the time to provide feedback. Any feedback coming from you is more than welcome a2800276.
Could you provide a link to the haskell and erlang packages you were referring to?
- iso8583-bitmaps and https://code.google.com/archive/p/erl8583/downloads . To be honest I think I overreacted a little in the description, those are not state of the art libs, they just have one good or two ideas.
My feeling is that a C implementation would bring the most value in the embedded space
- I want to create a solid thread-safe library that enjoys the benefits of C. Small memory footprint, Speed (true multi-threading env) and portability (embedded systems). I know I can do a more than acceptable work, but I'm afraid I'm not familiar with all the limitations of the embedded ecosystem. I'd love to hear more about these limitations.
I like your idea of having a 'portable' testing spec that could be reused both for the bindings as well as possibly other implementations.
- Oh that's nice to hear, yes, last year I was developing a solution for a local company and one of the fantasies I had was the one of having a portable spec.
by the way I'm using your ruby 8083 lib quite successfully, right now is handling ~20k trans/day. this is the product and the company: https://visanetdominicana.com/ncf-pos
where's a good place to discuss?
- my email is manuel@marcos.do, it can be Slack though. Btw for the next 3 days I'll be staying in a place with limited internet access, expect a delay in my responses.
Hi, wanted to seize the opportunity and provide some feedback (before there's even any code :)
Could you provide a link to the haskell and erlang packages you were referring to? I couldn't find anything that looks at all robust or anywhere near complete (https://hackage.haskell.org/package/iso8583-bitmaps-0.1.0.0, https://github.com/josepablocastro/efak ?) I'd be interested to see how they're doing things ...
Personal opinion: it would probably make a lot of sense to make the c lib as rudimentary as possible (i.e. avoiding mem allocation, libc usage, etc if possible). My feeling is that a C implementation would bring the most value in the embedded space (think terminal hardware, smartcard) and that using it to bootstrap a lot of binding libraries may be more hassle than it's worth.
I like your idea of having a 'portable' testing spec that could be reused both for the bindings as well as possibly other implementations.
Also: where's a good place to discuss? I never really know at github, this post doesn't really feel like an issue to me but would belong on a mailing list or something... Any preferences?