The Gal To Gal Foundation has a new web site and online campaign for the Gal To Gal Virtual Walk 2007. It aims to improve the lives of women diagnosed with Stage IV breast cancer and is expected to raise $1m. The site is due to be featured on the Martha Stewart Show on Monday, October 1st to a national audience in the United States.
The site it uses SWX RPC, with a SWX PHP back-end.
Jon MacDonald has a case study of the Gal To Gal Virtual Walk project, wherein he explains that the entire site was built in one-and-a-half weeks:
SWX is used extensively throughout the site to communicate with the back-end and database. This enabled the rapid development timeline, and made the process of storing and passing data through PHP seamless. I haven't seen any other true sites built with SWX, but rather small mash-ups and widgets, so I believe this is a first for the SWX project.
Read more about GalToGalWalk.org in my blog post and on Jon's case study.
Wouter Verweirder has released
a new tutorial on setting up and using CakeSWXPHP, the
SWX RPC implementation for the
CakePHP framework that is based on
SWX PHP.
In the tutorial, Wouter takes you through the process of creating a Flash blog, starting with the installation and setup of CakeSWXPHP.
The tutorial shows you how to create a database for your Flash blog and write the CakePHP code to store and retrieve data from it.
This is a comprehensive, intermediate tutorial that will be invaluable in teaching Flash developers who work with CakePHP how to get up and running with CakeSWXPHP.
Great stuff, Wouter! 
Read the CakeSWXPHP tutorial on Wouter's blog.
If you have deployed SWX PHP 1.0 or 1.0.1 (not the SWX PHP Deployment Bundle) to a public server, then please download
showsource.php.zip and unzip it into the
/php/services/_idvr/ folder on your server to fix a potentially exploitable security issue with the showsource.php file that displays the source code for your services in the browser.
The issue will also affect the SWX MAMP Bundle if you have deployed that to a public server (which you should not do in any case as MAMP is not secured for deployment).
Thanks go to Sébastien Ballesté-Antich for reporting the issue after discovering it on the SWX homepage. Normally, this should not affect you as you should only deploy the SWX PHP Deployment Bundle to a public server. (The SWX homepage runs an instance of the full SWX PHP package to demostrate the Start Page and other features). I've now patched the SWX PHP instance on the SWX homepage with this update.
The SWX PHP Deployment Bundle is a bare-bones version of SWX PHP that doesn't contain the fancy Start Page, etc., that the development version has.
To clarify, this is not a security issue with the SWX RPC gateway or assembler itself in the SWX PHP implementation but with an unrelated file that is used to display the source code of your PHP service classes through the browser when using the SWX PHP Start Page during development and it affects development versions of SWX PHP only.
The SWX PHP Deployment Bundle is not affected by this issue.
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/";
This is so cool: Jed Hurt has released Alpha 0.1 of SWX Ruby, the Ruby implementation of SWX RPC for Ruby on Rails.
Read more about SWX Ruby.
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.
generic paxil
christina ricci prozac nation
imitrex nasal spray
carisoprodol href
prozac
crestor
diflucan online
cialis compare levitra
cheap prednisone
phentermine no prescription
doxazosin 4 mg
celebrex canadian
paxil on line
prosac
effexor tablets
tramadol online
online pharmacy tramadol
levitra blog
herbal hoodia phentermine
lipator
diflucan 1
buy rimonabant
imitrex patent
crestor
diflucan 1
emea rimonabant
fluconazole diflucan
buy carisoprodol cheap online
buy cialis link
discount paxil
generic levitra online
order proscar
rimonabant
clonidine prescription
cheap proscar
imitrex online
purchase rimonabant
buy proscar
furosemide and digoxin
buy proscar
natural viagra
diflucan online
stopping prednisone
lipitor side effects
buy carisoprodol
proscar drug
generic imitrex
effexor antidepressant
buy carisoprodol
lipitor uk
In response to a possible PHP configuration-related issue where the
SWX PHP Start Page may not display correctly for some users, I've updated the SWX PHP and SWX PHP Deployment Bundle packages with a .01 (minor) release.
If you are affected by this, please download the latest release of SWX PHP.
The issue does not affect the SWX PHP MAMP Bundle, which remains at 1.0.
I want to thank Tom Beaver for reporting the issue to me in great detail and working with me to test the solution. Thanks, Tom!
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.
