If your Flex application will be used from
a web browser and not via the standalone player you shouldn’t have any
problems. It’s only if you’re trying to build an app that doesn’t
use a web browser.
Matt
From:
[email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Will Sargent
Sent: Monday, May 09, 2005 12:45
PM
To: [email protected]
Subject: [flexcoders] No stateful
objects on MacOS?
Hello all,
I'm a complete Flex newbie. I'm trying to
put together a RemoteObject
service, and came across this in the
documentation:
----------------
http://livedocs.macromedia.com/flex/15/flex_docs_en/wwhelp/wwhimpl/js/html/wwhelp.htm?href="">
Stateful objects
When you use the <mx:RemoteObject> tag, you
use the stateful-class type
to call methods on a class on the server. When you
access a Java object
using this syntax, the class is loaded on the server
and Flex maintains
state between method calls.
Flex uses J2EE server sessions to maintain the
state of stateful Java
objects. The server session feature depends on
session cookies. The
session cookie is sent automatically. If you want
to ensure that
non-cookie-handling clients have stateful access
to Java objects, you
can append the jsessionid to the URL. You
typically do this in a
JavaServer Pages (JSP) file by using the
response.encodeURL() method.
The server session feature is available on
Windows, Linux, and UNIX
versions of the stand-alone Flash Player, but is
not available on the
stand-alone Flash Player for the Macintosh
platform.
------------------
If the Macintosh platform doesn't support the
"server session" feature
and the "server session" feature is
needed to maintain stateful-class
RemoteObjects... does that mean that I can't use
stateful-object if I
want the Flex application to be available on
Macintosh?
Will.
Yahoo! Groups Links
|
