Re: DWR Scalabilty And Early Closing Mode

So does this issue prevent DWR from currently working at all with
Lightstreamer or Blaze DS?

Thanks
Ron

Joe Walker-3 wrote:
>
> Lightstreamer does a lot of stuff that DWR does not currently do, so I
> fully
> expect that it will scale better.  There is an issue to get DWR to use
> lightstreamer as a conduit: http://getahead.org/bugs/browse/DWR-49,
> however
> this is very low priority.
>
> Joe
>
> On Wed, Mar 19, 2008 at 4:00 AM, r123 <ronberna@...> wrote:
>
>>
>> So would DWR in Full Streaming or Early Closing mode running on Websphere
>> be
>> able to handle the 10,000 concurrent users that LightStreamer advertises
>> that it can handle?  Also, is it possible to integrate DWR with
>> LightStreamer or Flex Blaze DS servers?
>>
>>
>>
>> Joe Walker-3 wrote:
>> >
>> > DWR does a lot to protect the server against overloading. In the case
>> of
>> > Websphere, there is no custom plugin for their async servlet, so we
>> fall
>> > back to the servlet-api implementation which backs off connection
>> numbers
>> > to
>> > prevent overloading things.
>> >
>> > Early closing mode is there to prevent buggy proxies messing with the
>> > responses - it's not about reducing load.
>> >
>> > What kind of latencies are important to you? If you're ok with
>> latencies
>> > of
>> >> 60 seconds, then you can configure DWR to poll, which should reduce
>> the
>> > server load.
>> >
>> > Joe.
>> >
>> > On Sun, Mar 16, 2008 at 4:30 PM, r123 <ronberna@...> wrote:
>> >
>> >>
>> >> We have a project that will run on a Websphere 6.1 server that needs
>> to
>> >> send
>> >> data to the web client in real or near real time.  The data will be
>> read
>> >> from a JMS topic. We are considering using DWR "Reverse AJAX" to help
>> >> push
>> >> this data from the web server to the web client.  There are some
>> concerns
>> >> about how this would scale as well as failover.  There is also a
>> concern
>> >> about the "push" vs. "pull" concept.
>> >>
>> >> I read some about Early Closing Mode in DWR.  If I understood this
>> >> correctly, DWR will close the http connection after 60 seconds if
>> there
>> >> is
>> >> no activity.  A question I have is does it release the socket or
>> thread
>> >> once
>> >> that connection is closed?   Would this approach be able to scale to
>> >> thousands of clients or would a dedicated server component like Tibco
>> >> "Ajax
>> >> Messaging Service" which uses LightStreamer be needed in order to
>> handle
>> >> large numbers of clients?  The disadvantage I read about Early Closing
>> >> Mode
>> >> is that many clients may possibly try to re-connect at the same time.
>> >> How
>> >> big of an issue is this?
>> >>
>> >> Any ideas on this would be greatly appreciated.
>> >>
>> >> Thanks
>> >> r123
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/DWR-Scalabilty-And-Early-Closing-Mode-tp16080860p16080860.html
>> >> Sent from the DWR - Users mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@...
>> >> For additional commands, e-mail: users-help@...
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/DWR-Scalabilty-And-Early-Closing-Mode-tp16080860p16136629.html
>> Sent from the DWR - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
>

--
View this message in context: http://www.nabble.com/DWR-Scalabilty-And-Early-Closing-Mode-tp16080860p16472217.html

Sent from the DWR - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...