What other sites do flash and other web 2.0 components trust, by Google search or Google hacking the crossdomain xml file, you can find out some very interesting things about what sites are trusted by another site, and where API’s or other trusted widgets can come from, including advertising.

The Google hack is here, crossdomain.xml site:.com or feed in extension .com, .net, .org etc of choice.

This is the crossdomain.xml file from twitter as an example

allow-access-from domain=”*.twitter.com”
allow-access-from domain=”*.discoveringradiance.com”
allow-access-from domain=”*.umusic.com”
allow-access-from domain=”*.hippo.com.au”
allow-access-from domain=”*.ediecareplan.com”
allow-access-from domain=”*.yourminis.com”
allow-access-from domain=”*.korelab.com”

(more…)

Here is a mystery for folks. I’ve updated my parsing engine for coldfusionbloggers.org.

I’m using CFHTTP now so I can check Etag type stuff. I take the result text and save it to a file to be parsed by CFFEED.

But before I do that I check to ensure it’s valid XML. Here is where it gets weird. Charlie Griefer’s blog works with CFFEED directly, but isXML on the result returns false. But - I can xmlParse the string no problem. Simple example:
(more…)

Not many people know that ColdFusion ships with a HTTP spider that integrates with Verity. Unfortunately, this spider will only work with localhost as a server.

This means if you want to spider multiple sites, you can’t. Well, not without playing with your host headers. (More information on the Verity Spider and ColdFusion may be found here.) (more…)

While working on some bugs in the CFLib SnipEx server, Mark Drew sent me a great tip on how to clear the cache in CFEclipse.

Right now it is a manual process, but Mark will be adding a refresh option to the UI soon.

So to clear your SnipEx cache, drop down to the command line and….

1. Change to your Eclipse workspace. Mine was at /Users/ray/Documents/workspace

2. Change to .metadata/.plugins/org.cfeclipse.cfml/snipex

3. Delete all XML files

4. Restart Eclipse

That’s it.

During development it makes sense to just keep a window open there so you can do this a bit more quicker. (By development I mean if you are working on your own SnipEx server.)

So CFLib has had some issues with SnipEx, mainly with UDFs that don’t work well in the XML feed.

I’ve been removing the UDFs temporarily and this morning I just removed another another one. (more…)

Someone asked on the Model-Glue mailing list how to keep deal with keeping event handler names and URLs in views consistent, i.e., if they change an event handler name, how can they avoid having to change the string wherever it appears in links in their views.

Fusebox has long had a convention to deal with this known as XFAs - eXit FuseActions. The idea is to abstract the actual fuseaction name into a variable.

You specify all the exit points for a view as XFAs in the XML and refer to the variable in the view instead of hard-coding the fuseaction name. If you need to change the control flow - or the fuseaction name - you just change the XFA in the XML file and your views all pick that up.

Often Fuseboxers set common XFA values in the prefuseaction for the circuit or the global preprocess fuseaction for the application, making it very simple to manage exit points. (more…)