The tweets example you mention here: http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0/scala/stream-integrations.html#Integrating_with_External_Services Relates to the quickstart – reactive tweets: http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0/scala/stream-quickstart.html The tweets itself is just a mock, "imagine some source of tweets". You're right that we should explain what it is on the integrations page (would you like to submit a PR to help us with that? a :ref: link to the quickstart would help I think).
Should a Source be created every time a new object is deserialized from a particular queue? No. A source emits multiple elements. It's possibly an infinite source. A Kafka consumer that I looUked at extends ActorPublisher? Does that mean that if I have to wrap an actor around the client for the specific queue in order to be able to create a source from that? ActorPublisher is a helper class to implement a reactive streams Publisher. You don't need to extend it unless you want to imlpement a Publisher. It depends what you need, Maybe writing an AsyncStage (we'll document it soon, it's a rather advanced tool - https://github.com/akka/akka/issues/18018 ) would be useful for you? It's a very advanced Stage but may be just what you need - we'll do more docs about it soon as well (think of it "most people dont need it"). -- Cheers, Konrad 'ktoso’ Malawski Akka @ Typesafe On 16 July 2015 at 16:21:55, Alexander Zafirov ([email protected]) wrote: Hello, Before I explain my question I want to say I tried looking for a problem previously explored which relates to mine but didn't find anything. If I am mistaken please excuse me and if possible provide me with a link to the right thread :) I'm new to Akka Streams and am currently exploring the possibilities of integrating it's great capabilities when interacting with a queuing service as ones mentioned in the title. My use case with Akka Streams is to be able construct a source from an incoming message from the queue that I am subscribed to/am polling. Having went through the Akka docs, on the Integration page I found the sending emails to tweet's authors example come closest to my problem. We start with the tweet stream of authors: val authors: Source[Author, Unit] = tweets .filter(_.hashtags.contains(akka)) .map(_.author) It is unclear to me how these tweets come about? Furthermore after examining the Source object's apply methods I want to know: Should a Source be created every time a new object is deserialized from a particular queue? A Kafka consumer that I looked at extends ActorPublisher? Does that mean that if I have to wrap an actor around the client for the specific queue in order to be able to create a source from that? Thank you, Alex -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
