DWR

normal remote calls are delayed (waiting for reverse ajax polls) when using setOrdered(true)

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.2
  • Fix Version/s: 3.0.RC2
  • Component/s: Engine
  • Description:
    Hide
    > But I have those long latency time where nothing
    > happens. Why? No call to a remoted method is active
    > but only Comet.
    > Can someone clarify what happens here? I would have
    > expected that Comet is not affected to ordering issues.

    Just like Thomas says it seems like Reverse Ajax polls
    are included in the "ordered" mode in 2.0 (seems to be
    fixed in 3.0 HEAD), which causes all "normal" remote
    calls having to wait for the current poll to finish.
    Show
    > But I have those long latency time where nothing > happens. Why? No call to a remoted method is active > but only Comet. > Can someone clarify what happens here? I would have > expected that Comet is not affected to ordering issues. Just like Thomas says it seems like Reverse Ajax polls are included in the "ordered" mode in 2.0 (seems to be fixed in 3.0 HEAD), which causes all "normal" remote calls having to wait for the current poll to finish.

Activity

Hide
David Marginian added a comment - 06/Apr/11 5:11 AM

Mike, from the comments it looks like this is something that is fixed, is that correct?

Show
David Marginian added a comment - 06/Apr/11 5:11 AM Mike, from the comments it looks like this is something that is fixed, is that correct?
Hide
Mike Wilson added a comment - 21/Apr/11 9:05 AM

Right, closing!

Show
Mike Wilson added a comment - 21/Apr/11 9:05 AM Right, closing!

People

Dates

  • Created:
    19/Feb/08 2:50 PM
    Updated:
    21/Apr/11 9:05 AM
    Resolved:
    21/Apr/11 9:05 AM