• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Is there an overhead in RemoteEndpoint.Async versus RemoteEndpoint.Basic?

 
Ranch Hand
Posts: 47
IntelliJ IDE Firefox Browser Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

I am working on a project with a WebSocket connection. Currently I call Session.getBasicRemote().sendText(String) for answering requests. So far it works, but I was thinking about using RemoteEndpoint.Async for them. Most of the request will do fine when they are asynchronous.

But I was wondering, will this thread creating produce an unnecessary overhead? The typical length of a message is around 50-80 characters long. Soo.... What do you think? Will there be any benefits of using RemoteEndpoint.Async instead of RemoteEndpoint.Basic?

Thanks!
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic