Sockets go through the OS network layer.  I'm sorry you haven't seen the
Player sending cookies, in most of my scenarios using a Player that runs
in an HTML page I've seen the headers being sent across.

 

I'm also sorry that there isn't a published workaround for you right
now, but I don't think we consider it the best use of our time to
rewrite an HTTP stack in AS3 for this issue when we've been working with
vendors to find solutions.  I know you think that as a big company we
have infinite resources but we simply don't, and this is one of the
issues where we've had to make some tough decisions.  Believe me, I ran
meetings for multiple weeks on this issue alone to see if we could find
a better way.

 

Matt

 

________________________________

From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Paul DeCoursey
Sent: Wednesday, March 21, 2007 6:50 AM
To: [email protected]
Subject: [flexcoders] Re: WebService Fault Handling - Flash Player 9
Update

 

How are sockets implemented then? Also I have never seen the Flash
Player include the browsers cookies in requests. This has been a big
complaint of mine for a very long time. They only way I could get a
session shared with the browser was to pass in the session id using
External Interfaces.

And why can't you give us a workaround? Like a stack we can include in
our projects that isn't part of the player. This issue almost made
Flex/Flash irrelevant to my current project. I had to fight for weeks
to be able to use it. In the end I made some false promises that I
had hoped adobe would get it fixed soon.

If I had the time and resources I'd fix it myself.

--- In [email protected] <mailto:flexcoders%40yahoogroups.com>
, "Matt Chotin" <[EMAIL PROTECTED]> wrote:
>
> Well, the Player uses the browser's network stack so that it can be in
> sync with what the browser is doing (cookies) as well as reduce the
> amount of code we have to include in the runtime (size is critical as
> you know). In Apollo we need to use the system network layer so we
> actually hope to have more access to the information you're looking
for,
> but for the plugins we rely on the browser. Were we to write our own
> network layer in AS we would lose the browser integration that is
often
> important.
> 
> 
> 
> Matt
> 
> 
> 
> ________________________________
> 
> From: [email protected] <mailto:flexcoders%40yahoogroups.com>
[mailto:[email protected] <mailto:flexcoders%40yahoogroups.com>
] On
> Behalf Of Paul DeCoursey
> Sent: Tuesday, March 20, 2007 10:45 AM
> To: [email protected] <mailto:flexcoders%40yahoogroups.com> 
> Subject: [flexcoders] Re: WebService Fault Handling - Flash Player 9
> Update
> 
> 
> 
> I find it hard to believe that we can create our own implementation
> that would support this using sockets but the built in method requires
> browser vendor help.
> 
> --- In [email protected]
<mailto:flexcoders%40yahoogroups.com>
<mailto:flexcoders%40yahoogroups.com>
> , "Matt Chotin" <mchotin@> wrote:
> >
> > Unfortunately we cannot fix this without support from the browser
> > vendors. We are in discussions with them to try to have the right
> > information accessible to plugins in some of their next versions.
> > 
> > Matt
> > 
> > ________________________________
> > 
> > From: [email protected]
<mailto:flexcoders%40yahoogroups.com>
<mailto:flexcoders%40yahoogroups.com>
> [mailto:[email protected]
<mailto:flexcoders%40yahoogroups.com>
<mailto:flexcoders%40yahoogroups.com>
> ] On
> > Behalf Of paulwelling
> > Sent: Tuesday, March 20, 2007 8:59 AM
> > To: [email protected] <mailto:flexcoders%40yahoogroups.com>
<mailto:flexcoders%40yahoogroups.com> 
> > Subject: [flexcoders] WebService Fault Handling - Flash Player 9
> Update
> > 
> > 
> > 
> > Hello,
> > 
> > I just examined the latest FP9 Update Fixed Issues web page, and see
> > no mention of the WebService Fault Handling Issue (fault body not
> > passed to player) that has been discussed many times here...
> > 
> > This is a really big issue for people not using a proxy, and I'm
> > surprised that more of us haven't asked Adobe for this to be a
> > priority fix, or at least come up with a real work around.
> > 
> > Can someone tell me when this will be addressed..?
> > 
> > Thanks,
> > Paul
> >
>

 

Reply via email to