You can't open many HTTP based connections from any client. Off the top
of my head I think HTTP 1.1 suggests 2 connections and HTTP 1.0
suggested 4 connections. The flash player can't change this - it's up to
what is configured on each OS.
I see the batching as desired behavior because over a real
The player team wouldn't change this before Flex is released.
-Original Message-
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of sof4real03
Sent: Monday, April 17, 2006 6:01 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Do RemoteObject results still n
Reduced network overhead, repeated information can be included in an
outer envelope and you only take up one connection to the server instead
of multiple. The server should therefore be able to handle more
concurrent users.
Matt
-Original Message-
From: flexcoders@yahoogroups.com [mailto
I'm pretty sure we consider this desired behavior. I will file an
enhancement to turn off the batching but I doubt it will make it into
Flex 2.
Matt
-Original Message-
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of sof4real03
Sent: Monday, April 17, 2006 3:01 PM
Was that the workaround that involved using a unique endpoint URL to
avoid connection sharing?
If so, in FDS 2 you could create a new AMFChannel and assign it as part
of a service's channelSet:ChannelSet property.
import mx.messaging.ChannelSet;
import mx.messaging.Channel;
import mx.messaging.ch
It isn't up to the Flex RemoteObject feature... it's how the flash
player NetConnection works with AMF requests (and continues to work in
FP 8.5).
-Original Message-
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of sof4real03
Sent: Monday, April 17, 2006 3:15 PM
To:
6 matches
Mail list logo
