Hi Matt, Thanks, that looks good. There was another effort at a Redis client https://github.com/msainz/Redis.jl . At a first glance yours seem to have a greater coverage of the redis API.
If would be good to see some performance numbers. Is there a significant overhead of using a Julia client? Regards - Avik On Saturday, 29 November 2014 21:35:16 UTC, Matt Gushee wrote: > > Hi, Julia people-- > > First-timer here. I have been aware of Julia for a few months, and finally > decided to take the plunge, and it's a great experience so far. Most of my > recent programming has been in Scheme and Python, and, well, Scheme is both > endlessly fascinating and endlessly frustrating, and I'm kind of bored with > Python ;-). It's refreshing to find a language that Just Works [TM]. I > don't know how much is attributable to good language design and how much to > my own background (probably a bit of both), but it seems very easy to > reason about how things work in Julia. So, kudos to the devs. > > Anyway, I'm developing a Redis client, and I thought I'd solicit > constructive criticism on what I've done so far. I have a rudimentary > implementation that somewhat works. I haven't documented anything, but my > API is more or less a direct translation of the command set documented at > http://redis.io/commands . I've lowercased the names, and MULTIPLE WORD > COMMAND becomes multiple_word_command(); there is one case where I changed > the name due to a conflict with a Julia keyword ('type' -> 'value_type'). > > I have started on a test suite, and all tests pass for me, but the > coverage is minimal. My next step is to flesh out the test suite so as to > test as many functions as possible (some things are not unit-testable AFAIK > - e.g. 'DEBUG SEGFAULT' - think I'll skip that ;-) ) > > The project is at https://github.com/mgushee/Redis.jl. Let me know what > you think! > > -- > Matt Gushee >
