they just reopened it, if i'm not mistaken
--- In flexcoders@yahoogroups.com, "Jerome Clarke" <[EMAIL PROTECTED]> wrote:
>
> ok nevermind... I think I found it now... because I'm not installing
> BlazeDS... I just downloaded it and thought it all be there just
like the
> Flex SDK itself
>
> blazeds / resources / flex_sdk
>
> and then I had to extract the flex_sdk_3.zip which I thought was the
Flex
> SDK that recently got released and thats where it all is
>
> thanks... sorry for going off subject Bjorn and Josh
>
> and OH MY GOD didn't know they released all the code in the RPC in
"mx.rpc"
> and "mx.messaging"...
>
> thanks Adobe :p
>
> On Feb 7, 2008 7:21 AM, Jerome Clarke <[EMAIL PROTECTED]> wrote:
>
> > ok thanks but still can't see it...
> >
> > I've got Flex 3 Beta 3 SDK ( build 121207 ) and I found that but
it's only
> > locale files nothing more...
> >
> > and in BlazeDS directory... there is no folder called
"frameworks"... and
> > the latest one I can download from adobe labs is this file
> >
> > blazeds_b1_020108
> >
> > is that correct???
> >
> > thanks
> >
> >
> > On Feb 7, 2008 7:00 AM, Bjorn Schultheiss <[EMAIL PROTECTED]>
> > wrote:
> >
> > > sdks / frameworks / projects / rpc
> > >
> > > in blaze rc1
> > >
> > >
> > > On 07/02/2008, at 5:51 PM, Jerome Clarke wrote:
> > >
> > > hi... sorry to be off subject... but you said source... where
is the
> > > source... I don't see it anywhere except the JSP and Flex examples
> > >
> > > thanks
> > >
> > > On Feb 7, 2008 5:46 AM, Bjorn Schultheiss <[EMAIL PROTECTED]>
> > > wrote:
> > >
> > > >
> > > > Don't quote me..
> > > > I looked into the source for the first time when blaze rc1 was
> > > > released.
> > > > Its complicated.
> > > >
> > > > On ResultEvent is
> > > >
> > > > override mx_internal function callTokenResponders():void
> > > > {
> > > > if (token != null)
> > > > token.applyResult(this);
> > > > }
> > > >
> > > > Apply result is
> > > > mx_internal function applyResult(event:ResultEvent):void
> > > > {
> > > > setResult(event.result);
> > > >
> > > > if (_responders != null)
> > > > {
> > > > for (var i:uint = 0; i < _responders.length; i++)
> > > > {
> > > > var responder:IResponder = _responders[i];
> > > > if (responder != null)
> > > > {
> > > > responder.result(event);
> > > > }
> > > > }
> > > > }
> > > > }
> > > >
> > > > callTokenResponders is called by abstract invoker which also
> > > > dispatchers the result/fault events at the same time
> > > > mx_internal function dispatchRpcEvent(event:AbstractEvent):void
> > > > {
> > > > event.callTokenResponders();
> > > > if (!event.isDefaultPrevented())
> > > > {
> > > > dispatchEvent(event);
> > > > }
> > > > }
> > > >
> > > >
> > > > On 07/02/2008, at 4:11 PM, Josh McDonald wrote:
> > > >
> > > > You're right, I hadn't noticed that. That's actually kinda
strange.
> > > >
> > > > When are they called, and what actually initiates the
responders? Is
> > > > it before or after the data or error events are dispatched?
> > > >
> > > > -Josh
> > > >
> > > > On Feb 7, 2008 3:03 PM, Bjorn Schultheiss <
> > > > [EMAIL PROTECTED]> wrote:
> > > >
> > > > > One thing i don't like about addResponder() is that there is no
> > > > > removeResponder();
> > > > >
> > > > >
> > > > > On 07/02/2008, at 4:01 PM, Josh McDonald wrote:
> > > > >
> > > > > What's the prevailing wind / general thoughts on using
> > > > > token.addResponder vs adding event listeners, beside the "one
> > > > > request" vs "all requests" nature of it? Is one faster /
better / more
> > > > > common that the other?
> > > > >
> > > > > --
> > > > > "Good people will do good things, and bad people will do bad
things.
> > > > > But for good people to do bad thingsâ"that takes religion."
> > > > >
> > > > > :: Josh 'G-Funk' McDonald
> > > > > :: 0437 221 380 :: [EMAIL PROTECTED]
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > "Good people will do good things, and bad people will do bad
things.
> > > > But for good people to do bad thingsâ"that takes religion."
> > > >
> > > > :: Josh 'G-Funk' McDonald
> > > > :: 0437 221 380 :: [EMAIL PROTECTED]
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
