Sep 3, 2007
SWX PHP and SWX ActionScript Library Release Candidate 1 Released
There is a whole slew of changes in this update and you can find the whole list in the release notes for SWX PHP RC1.
One of the major changes is that SWX RPC calls can now return simple data types as opposed to the previous behavior which was to wrap simple data types in an array. This may break your existing applications, so please read these instructions for updating your SWX applications to SWX PHP RC1.
Among the highlights of the RC1 release is the release of the SWX Flickr API, which has been available on the Public SWX Gateway for a little while now. The SWX Flickr API implements the full Flickr API and has some additional utility methods that make it the easiest way to work with Flickr in Flash. Take a look at the miniflickr Flash Lite sample application that comes with this release to learn how to work with the new Flickr API as well as some of the advanced features of the SWX ActionScript Library like the ExternalAsset and LoadManager classes.
SWX PHP RC1 has two more new APIs: The Jaiku API and Numpa API (Numpa is the Netherlands version of Twitter), both by my dear friend Folkert Hielema. You can find Folkert's other SWX-related work, as well as the work of other community members, in the new SWX Showcase.
You can explore and test all of the SWX APIs online using the SWX Service Explorer.
The SWX Data Analyzer has also been updated and now supports the display of simple data types correctly. It also displays debug information in a clearer manner.
With the RC1 release, the SWX ActionScript Library is available as a separate download. This means that if you don't want to write your own server-side classes, you don't have to download the full SWX PHP package just to use the high-level ActionScript classes.
Unless there are any major issues discovered in the next few days, Release Candidate 1 is going to be very close to the final release version of SWX PHP and the SWX ActionScript Library. If you do notice any issues, please report them to me. SWX PHP is now in feature freeze and only critical bugs will be fixed at this point (no new feature requests, etc.) In the next few days, I'm going to be updating the documentation, making some aesthetic changes, and recording more screencasts to prepare SWX PHP for the Version 1.0 release next week.
We're very close to Version 1.0, and that's just the beginning! 
phentermine on line
digoxin interaction
commercial levitra
buy phentermine online
viagra online
celebrex coumadin
buy carisoprodol diazepam online soma
furosemide and digoxin
rimonabant depression
side effects of furosemide
effects hoodia plant side
doctor lipitor vs zocor
carisoprodol medicine
rimonabant 20mg
buy crestor online
lipitor atorvastatin
side effects of furosemide
order neurontin
cheap effexor
iv furosemide
melphalan prednisone
venlafaxine effexor
bumetanide furosemide
free levitra
slimciti hoodia
digoxin levels
buy proscar
cheap levitra online
crestor canada
proscar medication
buy lipitor online
paxil attorney
buy cheap levitra online
kamagra oral jelly
digoxin interactions
generic prozac
cheap viagra
crestor
celebrex capsules
prednisone
doctor lipitor vs zocor
generic tramadol
carisoprodol href
side effects of proscar
discount lipitor
crestor info
proscar online
cheapest tramadol
effexor 37.5 mg
proscar uk
[...] For a detailed description of the release, please see the SWX PHP RC1 announcement on swxformat.org. [...]
Heya Aral,
Thanks for all the hard work on SWX. I have been playing around with the past few versions and I’m about to embark on a larger-scale site using SWX. I’m wondering if you could make a small note on what performance levels one can expect under high usage loads? Similar to AMFPHP? Has any part of the project been optimized for heavy usage? Any insight here would be helpful.
Thanks!
Hi Jon,
I haven’t load tested AMFPHP but Googling around, I found a couple of load statistics from Adobe. An Adobe case study states that Flash Remoting with Coldfusion MX scaled to support 200 concurrent users. Christophe Coenraets states on a blog post that they supported 1,500 concurrent users in a cluster of 8 servers (~187 concurrent users per server) with FDS.
I just ran some quick load tests using ApacheBench (ab) on my MAMP-based development server on my MacBook pro (note: *not* an optimized deployment server). In the test, the SWX gateway handled 250 concurrent users each requesting the list of 100 most recent Flickr photos.
The actual test I used was:
It looks like SWX should scale adequately in comparison to Flash Remoting. The Public SWX Gateway is getting hit quite a bit and has been holding up without issues and I haven’t run into any performance issues with the various APIs at the moment.
[...] PHP ve SWX Action Script kütüphanesi RC1 PHP Ruby yi döver mi? Podcast: Davey’s API Rant JASON sadece Ajax için mi? Ruby öğrenmek [...]
Hello Aral,
I’d been implementing something sorting and using an unusually large dataset (10,000 ) derived from a file system, and had tinkered with swx so I can have a file on the server that will allow flash to report bytesLoaded. It was only when I got an initial dataset loaded that I realised the flex LocalConnection hack necessary to get the data. Could you mention how the avm2 generator is coming along?