Give me cookies first, oreos !!! I'm sure I will, it is just a matter of time and spend sometime migrating, I just initially didn't have the time to be the first with headaches, That said I think in a couple of weeks I should be moved over.
Thanks to Akka team and contributors for all the effort put here, Guido. On Friday, March 18, 2016 at 4:06:08 PM UTC, Konrad Malawski wrote: > > New Java API is comign in very large steps, I think the new one you'll > like a lot and come back to plain Akka :-) > > > On Mon, Mar 14, 2016 at 5:13 PM, Guido Medina <oxy...@gmail.com > <javascript:>> wrote: > >> Also there are other aspects you should be aware like back-pressure which >> is better handled at Akka, to be fair both teams are awesome (Vert.x and >> Akka) >> But in my case my decision was influenced by the fact that my company has >> 1 man team for the project => me, so I need things to be done faster than >> normal workflow. >> Also I'm streaming many small messages (prices) and they need to get to >> the client fast so speed is an important factor for me. >> >> HTH, >> >> Guido. >> >> >> On Monday, March 14, 2016 at 4:03:41 PM UTC, Guido Medina wrote: >>> >>> Vert.x is just another reactive framework, I found it easier to use than >>> Akka HTTP for Java that's all, and I think (at least today) it is faster. >>> I cannot really recommend you one or the other just state what I know, >>> the decision is still yours. >>> I know Akka team works very hard on improving things so always be open >>> and treat my recommendation as a biased opinion. >>> >>> HTH, >>> >>> Guido. >>> >>> On Monday, March 14, 2016 at 11:50:57 AM UTC, Alan Klikic wrote: >>>> >>>> Hi Guido, >>>> >>>> thank you for the shared info. >>>> We are planing to use Google's Protocol Buffer ( >>>> https://developers.google.com/protocol-buffers/) instead of JSON. >>>> You recommend using Vort.x with Netty implementation instead of Akka >>>> HTTP for now? >>>> >>>> Br, >>>> Alan >>>> >>>> Dana srijeda, 9. ožujka 2016. u 11:11:43 UTC+1, korisnik Guido Medina >>>> napisao je: >>>>> >>>>> *Disclaimer:* The Akka HTTP performance on that page is outdated, >>>>> now; if Akka HTTP is around 75% performance of Play 2, you can guess >>>>> where >>>>> it would be on that list. >>>>> >>>>> On Wednesday, March 9, 2016 at 9:58:04 AM UTC, Guido Medina wrote: >>>>>> >>>>>> Hi Alan, >>>>>> >>>>>> I hope the Akka/Java example has helped, I will eventually migrate to >>>>>> it when Akka HTTP websockets performance gets better compared to Vert.x >>>>>> with Netty implementation: >>>>>> >>>>>> >>>>>> https://www.techempower.com/benchmarks/#section=data-r12&hw=peak&test=json >>>>>> >>>>>> If you notice on my original source code (in case you still need the >>>>>> answer), I'm passing the upgraded socket to the actor so it should just >>>>>> be >>>>>> a final property of the newly created actor. >>>>>> Such socket has a write method, I'll post here again another -and >>>>>> working- example with two paths, notice that for each path a different >>>>>> type >>>>>> of actor is created and the upgraded socket is part of the actor creator: >>>>>> >>>>>> >>>>>> vertx.createHttpServer().requestHandler(request -> { >>>>>> switch (request.path()) { >>>>>> case "/price": { >>>>>> final ServerWebSocket socket = request.upgrade(); >>>>>> final ActorRef actorRef = context.actorOf(Props.create(new >>>>>> PriceWebsocketCreator(TargetSupervisor.this, socket))); >>>>>> socket.setWriteQueueMaxSize(1024). >>>>>> handler(event -> actorRef.tell(event, NO_SENDER)). >>>>>> closeHandler(event -> >>>>>> actorRef.tell(PoisonPill.getInstance(), NO_SENDER)); >>>>>> log.info("Price websocket connection from '{}' to '{}' >>>>>> established.", socket.remoteAddress(), socket.localAddress()); >>>>>> break; >>>>>> } >>>>>> case "/ticket": { >>>>>> final ServerWebSocket socket = request.upgrade(); >>>>>> final ActorRef actorRef = context.actorOf(Props.create(new >>>>>> TicketWebsocketCreator(TargetSupervisor.this, socket))); >>>>>> socket.setWriteQueueMaxSize(1024). >>>>>> handler(event -> actorRef.tell(event, NO_SENDER)). >>>>>> closeHandler(event -> >>>>>> actorRef.tell(PoisonPill.getInstance(), NO_SENDER)); >>>>>> log.info("Ticket websocket connection from '{}' to '{}' >>>>>> established.", socket.remoteAddress(), socket.localAddress()); >>>>>> break; >>>>>> } >>>>>> default: >>>>>> request.response().setStatusCode(400).end(); >>>>>> } >>>>>> }).listen(config.getInt("http.port"), >>>>>> config.getString("http.host")); >>>>>> >>>>>> >>>>>> HTH, >>>>>> >>>>>> Guido. >>>>>> >>>>>> On Tuesday, March 8, 2016 at 10:03:23 AM UTC, Alan Klikic wrote: >>>>>>> >>>>>>> Hi Guido, >>>>>>> >>>>>>> this post helped me allot. Thanks. >>>>>>> How can I send message from the Actor to the "connected" websocket? >>>>>>> As a response to initial message received from websocket and as a >>>>>>> standalone/push message from Actor to websocket? >>>>>>> >>>>>>> Thank you in advance. >>>>>>> >>>>>>> Br, >>>>>>> Alan >>>>>>> >>>>>>> Dana srijeda, 24. veljače 2016. u 13:36:17 UTC+1, korisnik Guido >>>>>>> Medina napisao je: >>>>>>>> >>>>>>>> While Akka HTTP is accessible to Java 8 users I decided to go for >>>>>>>> an alternative which I was trying to avoid but at least I know is of >>>>>>>> high >>>>>>>> performance and it fits right my needs. >>>>>>>> When a connection is upgraded to websocket it is passed to an >>>>>>>> actor, also every message sent is forwarded to an Actor, Java 8 code >>>>>>>> snippet below: >>>>>>>> >>>>>>>> vertx.createHttpServer().requestHandler(request -> { >>>>>>>> if ("/signal".equals(request.path())) { >>>>>>>> final ServerWebSocket socket = request.upgrade(); >>>>>>>> final ActorRef actorRef = context().system().actorOf( >>>>>>>> // Using an internal non-blocking bounded mailbox with >>>>>>>> capacity reserved (similar to LMAX) >>>>>>>> Props.create(new SignalWebsocketCreator( >>>>>>>> SourceSupervisor.this, socket)).withMailbox("bounded-mailbox-1024") >>>>>>>> ); >>>>>>>> socket.setWriteQueueMaxSize(1024). >>>>>>>> handler(event -> actorRef.tell(event, noSender())). >>>>>>>> closeHandler(event -> actorRef.tell(PoisonPill. >>>>>>>> getInstance(), noSender())); >>>>>>>> log.info("Websocket connection from '{}' to {} >>>>>>>> established.", socket.remoteAddress(), socket.localAddress()); >>>>>>>> } else { >>>>>>>> request.response().setStatusCode(400).end(); >>>>>>>> } >>>>>>>> }).listen(config.getInt("http.port"), config.getString( >>>>>>>> "http.host")); >>>>>>>> >>>>>>>> >>>>>>>> Hope it helps some Java fellows that are stuck on this matter, not >>>>>>>> ideal if you want to strictly stick to Akka like I wanted though it is >>>>>>>> still a quick, simple and efficient solution, >>>>>>>> >>>>>>>> Guido. >>>>>>>> >>>>>>> -- >> >>>>>>>>>> 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 akka-user+...@googlegroups.com <javascript:>. >> To post to this group, send email to akka...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Cheers, > Konrad 'ktoso' Malawski > Akka <http://akka.io/> @ Lightbend <http://lightbend.com/> > -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
