With Flex 2.0 it is possible to connect directly from
client to mail servers, both IMAP or POP3. I have actually built some
prototypes to prove it out but have not taken it further. I imagine that
you will start to see some mail API's popup from different
developers.
Kevin
From:
The event broadcaster keeps a map of event types and the event listener. By
creating a new Delegate object everytime you are creating a new Listener.
So the broadcaster can no find the previous one to remove. If you want to
keep the Delegate ref stuff going. Try this:
class
I believe that this is done by the skin. So in most cases it is in
mx.skins.halo.RectBorder
-Original Message-
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of JesterXL
Sent: Monday, November 07, 2005 4:37 PM
To: Flexcoders
Subject: [flexcoders] DropShadow in 1.5
Title: AMF Protocol
This occurs when yourclient is notsending the
proper Content-Type header or if there is a parsing error. For example you
could see this if someone accessed the amf gateway directly with a
browser.
From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf
comparison simple POC apps to real world ones.
As you move your application towards use of stateful datasets and other
large transfers you will find yourself using HTTPRequests and WebServices
more often.
Sincerely,
Anatole Tartakovsky
- Original Message -
From: Kevin Langdon [EMAIL
Assuming you have a java backend, openAMF is your best
bet. It will require some tweeking to work with Flex RemoteObject tags but
should work out of the box with standard mx.remoting.*
classes.
From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Clint
ModienSent:
- AMF is binary data passed over standard HTTP request and responses. So
you should not have any problem with packet filtering.
- You can turn on GZIP compression with remoting just as you cand with
SOAP. That means it be even smaller. Remoting cuts out all the extra
metadata so its always
This would work, but you need two
welcomeMessage variables initApptwo() is just overwriting the first should be:
public function initApptwo() {
mySO2 = SharedObject.getLocal(mydata2);
welcomeMessageTwo = Hello + getNametwo();
}
and
mx:Label id=label2
text={welcomeMessageTwo}
Title: Mensagem
Your problem is that the Compositions
initialize and creationComplete events will fire before the Application
initialize event. Most components initiate all of their components in their
own init and it is not until they are finished that they will fire the
initialize
If your talking about right clicking on the Flash Player and going to
Settings-Local Storage tab. This is local storage for shared objects, not
for media like images. Images are stored in the browser cache and would
need to be cleared through your browser.
-Original Message-
From:
You probably want to look into the XMLSocket object.
This can make a connection back to a server and maintain it. A0 byte
is sent between requests and response without the connection being
dropped. Those requests and responses are xml and could be used for
messaging or keep alives to
Your contextroot needs to look like this: -contextroot /[webappName]
It takes a little while to get the properties set correctly for mxmlc but
once you do it works great.
You also might want to check this out:
http://www.deitte.com/archives/2005/09/speeding_up_mxm.htm to take advantage
of class
WARNING: This message contains little-to-no helpful information and for the
most part is a rant.
The problem with Flex pricing isn't the price itself. The problem is it's
model. Most development I have seen is only using Flex as a compiler, not a
service. Most applications would actually
13 matches
Mail list logo
