HangFire.Redis incompatible with ServiceStack 4.0

[peters]

Unable to install if using ServiceStack.Redis.

It's no big deal for us since we can just fallback to Sql Azure but this should be fixed anyway.

[odinserj]

Yep, and since ServiceStack 4.0 uses another licensing strategy, there should be both support for 3.x and 4.x versions. Or maybe Redis storage should use StackExchange.Redis library instead. I'll choose the solution, but a bit later.

[Tazer]

Any plans on making the switch soon ?

[Caldas]

ServiceStack 4 has a different license. I don't think it's a good idea to use it

-----Mensagem Original-----
De: "Patrik" notifications@github.com
Enviada em: ‎26/‎08/‎2014 11:49
Para: "HangfireIO/Hangfire" Hangfire@noreply.github.com
Assunto: Re: [Hangfire] HangFire.Redis incompatible with ServiceStack 4.0(#122)

Any plans on making the switch soon ?
—
Reply to this email directly or view it on GitHub.

[Tazer]

@Caldas I'm with you on that,

I was referring to switching to StackExchange.Redis

[ghuntley]

Hmm. Ran into this today for now just using SQL Azure as workaround. Have SS license and I'm using SSv4.Redis but if you need to go StackExchange.Redis then either way. - Subscribing.

[kieranbenton]

I would also +1 for using StackExchange.Redis, its had some initial teething problems but it is now very stable and very fast, as well as having barely any dependencies.

Anything we can do to help @odinserj?

[TheCloudlessSky]

👍 For the switch. I've been porting my projects to use StackExchange.Redis.

I pulled down Hangfire to see if I could start ripping it apart to use StackExchange.Redis. The most glaring problem to port it over will be the fact that currently Hangfire uses blocking pop/push commands, which StackExchange.Redis doesn't support because of multiplexing.

I'd be glad to help port this over if we can collectively decide how to implement this.

[sjwoodard]

@TheCloudlessSky, I'm able to help as well.

[sqmgh]

I haven't gone through all the code to see for certain, but if it's only using the blocking pop/push to wait for the next item to process, why not use pub/sub a method similar to what is described on the linked StackExchange.Redis page?

I think that for licensing reasons a StackExchange version is worth having. Even if it's only in addition to the ServiceStack one.