why does it say header-only library when there are cpp files and makefile?

[patefacio]

Sorry - never mind - had not actually looked at the code well enough. Interesting setup to allow lib or header only.

[nekipelov]

Makefile is used for compile examples. There are cpp files to create shared library if you need. But you can use redisclient like a header-only library.

[patefacio]

I see - thanks. Pretty cool.
From: Alex Nekipelov notifications@github.com
To: nekipelov/redisclient redisclient@noreply.github.com
Cc: Daniel Davidson dbdavidson@yahoo.com
Sent: Tuesday, December 9, 2014 2:08 PM
Subject: Re: [redisclient] why does it say header-only library when there are cpp files and makefile? (#2)

Makefile is used for compile examples. There are cpp files to create shared library if you need. But you can use redisclient like a header-only library.—
Reply to this email directly or view it on GitHub.

[patefacio]

As a follow up question: Is there a mechanism to pass binary data? All command variants take strings. I imagine there is a way to stuff a struct into a string (assuming no pointers/aliasing), but curious if you have tried it?

According to this http://stackoverflow.com/questions/7064822/how-to-push-binary-data-into-stdstring pushing binary data into a string is a bad idea, though.

[nekipelov]

As a follow up question: Is there a mechanism to pass binary data? All command variants take strings. I imagine there is a way to stuff a struct into a string (assuming no pointers/aliasing), but curious if you have tried it?

If you want to store/restore structures and classes, you need some kind of https://github.com/nekipelov/cborcpp, protobuf, boost::serialization. After serialization you can store data in redis.

According to this http://stackoverflow.com/questions/7064822/how-to-push-binary-data-into-stdstring pushing binary data into a string is a bad idea, though.

Because the first implementation used a text protocol. You are right, now I need new interface for binary arguments.

[patefacio]

Ok - for now I'll go with some serialization.

I've got a lot of what I need working with redisclient - but all my calls so far are fine being async. Maybe I'm missing something, but is there an obvious way to do a synchronous call. For example,

redis_client_.command("LRANGE", Cmd_key, "0", "-1",
                      [&](const RedisValue &redisValue) {
   ...
});
std::cout << "OOOPS" << std::endl;

This call is failing with a protocol error. I'm not sure - but I suspect it is because I'm trying to do other stuff on the redis client before this has completed. How can I make sure the handler runs before the print statement?

Thanks
Dan

[nekipelov]

This call is failing with a protocol error

Can you provide full example?

[patefacio]

Unfortunately I had to switch libraries due to this and another issue. The commit that did the switch is: patefacio/RedisExchange@f667b2a

If you get the code prior to that you will have a full example. As I recall, at a minimum there was a timing issue/race condition at startup. If you look at this code https://github.com/patefacio/RedisExchange/blob/8dd3cbf8ca2055bc565b8b6ca1111afbdac5cde9/exch/cpp/app/exch_server/exch_server.cpp#L111-L117
it is fairly straightforward. But for it to even get through startup correctly I found I needed to throw in a current thread sleep for a second or so before L117. Otherwise it would get some sort of state error. I think the issue is related to there being multiple queues involved and the approach of trying to support pub/sub in the state-machine that looks to cater to connected (i.e. state of NotConnected, Connected, Subscribed, Closed). By combining states of pub/sub with connected, off the bat there was an issue of connecting and subscribing to multiple channels.

Then with the sleep statement allowing it to get past startup I got an error similar to: #4

[nekipelov]

I can not reproduce your problem.