Category Archive for ‘FAQ’ at SWX: SWF Data Format

Archive for the 'FAQ' Category

Can I use a folder other than /php/services to hold my SWX PHP service classes?

Published

on September 18, 2007

. 0 Comments

You sure can. All you need to do is change a setting in the SWX configuration file (swx_config.php). You can find the file in the php folder.

In it, just change the $servicesPath variable to point to where your services are (relative to the SWX gateway).

// Service Path: Put your service classes in this folder.
// Is relative to the SWX gateway (swx.php).
$servicesPath = "services/";

Why am I getting Security Sandbox Violations in the Flash IDE when running the sample applications or my own applications?

Published

aral

on September 13, 2007

in FAQ, SWX ActionScript Library, SWX PHP and SWX RPC

. 1 Comment

Summary: This warning only occurs when testing your applications from the Flash IDE. Cross-domain data exchange will work correctly when you run your applications from a web server. You can ignore this warning.

SWX RPC lets you to make cross-domain data calls (you can turn this off by setting the allowDomain option in the SWX PHP configuration file at php/swx_config.php to false). This means, for example. that you can have a SWF running on your development server or on your shared host somewhere and you can still consume the SWX RPC services (APIs) on the Public SWX Gateway on swxformat.org.

The Flash IDE, however, will display a Security Sandbox Violation when you run SWX applications in the IDE. This is because applications that run in the IDE use the file:// protocol as opposed to http://. Rest assured that your applications will work correctly when tested from a web server using the http:// protocol.

In short, you can safely ignore this warning.

For a longer explanation, read on.

The way SWX RPC enables cross-domain data exchange is by writing an allowDomain statement to the exact URL of the SWF that called it (your application) in the SWX data SWF that it sends back. The SWX ActionScript Library sends this URL in the SWX RPC call for you.

If you are using the native method via loadMovie(), you need to send the value of _url in a parameter called url in your SWX RPC call manually. Alternatively, when using the native method, if you don't send a url parameter, you can specifically allowDomain the loaded SWX data SWF from the main application and it, in turn, it will allowDomain its parent (your application) if it doesn't receive the url. This second method is discouraged, however, as the SWX data SWF should not require access to your application (if only does so to allow your application access to itself by calling allowDomain on _parent) and a fake SWX data SWF from an untrusted SWX RPC gateway could possibly access data and/or alter your main application when using this method.

To summarize, you can ignore this warning and you should either send a url parameter when using the native method via loadMovie() in SWX RPC or, even simpler, use the SWX ActionScript Library when your applications need to access data across domains.

Why is my SWX PHP Start Page messed up?

Published

aral

on September 12, 2007

in FAQ and SWX PHP

. 0 Comments

Tom Beaver reported that his SWX PHP Start Page was broken when he installed SWX PHP 1.0 under Apache on OS X although it was working fine with the SWX MAMP Bundle. After some investigation, I realized that it was because I was using PHP short tags in Version 1.0. If short tags are turned off in the PHP configuration file, the SWX PHP Start Page will not display correctly.

You should only run into this problem if you downloaded SWX PHP on September 11th or 12th (GMT) and your PHP instance is configured to disallow short tags.

If this problem affects you, please download the latest release of SWX PHP (Version 1.01 or later) which has been updated to use long tags throughout the SWX PHP Start Page.

Althernatively, you can turn short_open_tag on in the PHP configuration file (php.ini). Instructions on how to do this are available in the PHP Manual.

Why are my string values sometimes incorrectly interpreted as numbers in the SWX Service Explorer?

Published

aral

on September 12, 2007

in FAQ and SWX Service Explorer

. 0 Comments

When entering string values for method arguments in the SWX Service Explorer, please enclose them in quotation marks, especially if they contain numbers. Otherwise, strings that start with numeric digits or are made up of a long sequence of numeric digits (such as IDs, etc.) will get interpreted as a number.

You can read more about this issue in the post titled Question: When's a string not a string.

This is a known issue and one that I will hopefully be addressing in the near future (post 1.0). In the meanwhile, to be on the safe side, please enclose all string values in the SWX Service Explorer in quotation marks.

SWX: SWF Data Format

Archive for the 'FAQ' Category

Can I use a folder other than /php/services to hold my SWX PHP service classes?

Why am I getting Security Sandbox Violations in the Flash IDE when running the sample applications or my own applications?

Why is my SWX PHP Start Page messed up?

Why are my string values sometimes incorrectly interpreted as numbers in the SWX Service Explorer?

Search

About

Latest

Archives

Categories