The amount of time to refactor this code, and I am referring to enterprise applications not your Mom’s blog.
XSS is a real threat and by attempting to solve this issue we may all have to create a better architecture for our clients.
Yes, yet another Twitter client. Does the world really need another Twitter client? Probably not. But this particular client was created based on a challenge that was issued by a fellow developer. The challenge – create a Flex app that uses a social networking service, and has at least one custom component, all in five minutes or less.
Here is the source code download, go ahead and tool around with it: Flex 5 Miute Challenge Source Code
So go ahead and have some fun, get together with some developers and tryout the ‘Flex 5 Minute Challenge’
Since my buddy and I made this up we came up with these rules, feel free to change them:
Flex application must utilize any service provided by a publicly available social networking site.
The application must contain at least one custom component.
Time begins as soon as you start writing code and the app must be published as a release build before 5 minutes is up.
That’s it, it’s fun, give it a shot.
So here it is:
[kml_flashembed publishmethod="static" fversion="10.0.0" useexpressinstall="true" movie="http://www.uiandtherest.com/ui/share/TwitterSearch.swf" width="500" height="300" targetclass="flashmovie"]
RESTful services, ah the thought of leveraging the HTTP protocal to make web service development much simpler than the ‘ole SOAP. But there is a problem, if you are a Flex or Flash developer that relies on the Flash Player. You see, staying true to the methodology and spirit of RESTful services means that an HTTP Status Code of 404 actually means something. It means the resource that was requested was not found. So in a RESTful service you may call a phone book service that returns a person and their phone number. Well if that person does not exist the REST service returns an HTTP Status Code of a 404. Get it? Got it? Okay.