It's not all that difficult, since io-streams has attoparsec support and aeson is an attoparsec parser... coded directly in the input box, I don't have io-streams installed so I can't see if this typechecks:
import Control.Applicative
import Data.Aeson
import Data.ByteString
import System.IO.Streams
import System.IO.Streams.Attoparsec (parseFromStream)
parseJSONFromStream :: FromJSON a => InputStream ByteString -> IO a
parseJSONFromStream = parseJSON <$> parseFromStream json'
Re:Haskell: http-streams and Aeson
by joshrotenberg on Saturday June 01, 2013 @11:46AM
(#5804429)
I started looking at attoparsec after the post. Thanks, I'll look closer and see if I can figure it out.
Re:Haskell: http-streams and Aeson
by joshrotenberg on Saturday June 01, 2013 @12:35PM
(#5804657)
Found this: https://github.com/RobinKrom/Mtgox/blob/master/src/Mtgox/Htt...
receiveResponse con (\_ i -> parseFromStream json i))
This seems to work but without the benefit of being marshalled into my type.
The `parseJSON <$>` bit in my sample converts it to your type. If you don't like the infix applicative it could be written as:
receiveResponse con (fmap parseJSON . parseFromStream json)
Re:Haskell: http-streams and Aeson
by joshrotenberg on Saturday June 01, 2013 @11:44AM
(#5804417)
Yeah, I figured that defeated the benefit of streaming. And I agree, withConnection is cleaner, I'll add that if I do a followup (which I think I will given all the good advice I'm getting from HN). Thank you!
Fixing this is probably beyond the scope of a simple walkthrough. I suspect it could be managed using unsafeInterleaveIO to translate between the io-streams chunks and the lazy bytestring chunks. Might be a nice thing to ask the io-streams developers to add. (Dealing with resource finalization could make it tricky though.)
On a less esoteric note, fetchQuakes would be improved by using withConnection. This would make it shorter, and ensures the stream is closed if there's an error.