On 27/02/2015, at 11:47 PM, Richard Cyganiak wrote:

> Just what I love as the first thing in my inbox on an early Friday morning: A 
> nine-page, highly technical report that makes my caffeine-deprived head hurt, 
> and ends with a declaration that the author has already made it to the 
> weekend! ;-)
> 
> Jokes aside, thanks for this, Paul. Do you think it would be possible to 
> extract from this:
> 
> 1. Any Issues (bugs, feature requests) against D2RQ, stating what we should 
> change/fix? These should go here: https://github.com/d2rq/d2rq/issues

Done. https://github.com/d2rq/d2rq/issues/265

> 2. Something tutorial-like that’s clear enough to share on the D2RQ wiki? 
> https://github.com/d2rq/d2rq/wiki

On my list :)

Just to restate it - the horrible, intractable difficulties I was having were 
caused by using an older version of SDB. The newer version used the same 
version of ARQ as D2RQ, and it all seems to work fine.


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
d2rq-map-devel mailing list
d2rq-map-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/d2rq-map-devel

Reply via email to