dorkie dork from dorktown wrote: > One of the open source solutions I occasionaly use *cough* *cough* > *drupal* *cough* has a mod redirect / mod rewrite htaccess file (i'm > combining words). Any url that is entered into the site gets rewritten > or redirected. It is a dynamic system that allows you to dynamically > redirect to the content you want without hard coding paths or > directories. > > So you would create a dynamic page (doesn't really exist - only in the > database) and then an alias to reach it. For example, > www.test.com/myalias <http://www.test.com/myalias>. Actually a lot of > systems use this (wordpress, etc). > > All urls entered in to the site would be redirected to index.php. At > this point you could with the super awesome power of server side code, > deliver page links dynamically and content dynamically. I recently did > a project with FXT and did exactly that. You pass the data as an xml > model into a script tag under the body tag. Search engines pick this > up. My Flex app pulled this xml in and then used it as a dataprovider > for numerous controls. > > I've asked in the wish list for Macromedia at the time before it was > Adobe to let us specify the type of extension for the published html > wrapper. Right now if you click publish or run it creates a HTML page. > So somewhere in the options it would be nice to choose the page > extension type (php, asp, jsp, etc) of the page we are publishing. > I've also investigated and requested a way to pick my template page > that Flex finds and then replaces the tokens which it is looking for > inside of it. This may all be possible already. I've been mostly only > learning the API, mostly. > > Now that I've had a chance to think about it a default Adobe Page and > Link Management admin site might be the solution. It would be created > and deployed to bin or bin-admin with every project. Then you would > upload that to the server along with the contents of your bin > directory. A developer could login to it on the server. The Adobe Page > Manager would use an xml file or database to create the aliases. The > alias would be for different states in a Flex app. When you create an > alias there would be a place where you could call the services or page > associated with that state and alias. It would then wrap that content > in a xml tag like in FXT for indexing. You could also pass any links > back to the page. The content and links would be in the noscript / > script / area of the page and not be visible to the user but it would > be visible to the search bots. Because it uses a single page index.php > and .htaccess mod rewrite it would redirect all traffic to the single > index page (php, asp, java). That page would take that url alias, > search the xml file or database and serve up the appropriate content > (in the background hidden to users). I hope that makes sense. > > It would manage aliases, content for that alias, links for the alias > and state to pass to the embedded flash swf. I can actually imagine > how it would work. Hmm.. I'm not sure I understand exactly what you are talking about, but let's see if this is close:
1. Set up the homepage to pull dcontent from the database using whatever server side technology (php/asp.net, etc, over WebServices/FMS, etc.) - front loader style (design pattern). 2. Set up a 404 handler (using .htaccess or iisadmin) to detect what url was passed in - say domain.com/section/contentid, and redirect to homepage. (How would the search engine deal with something like that - would it just keep replacing the index information for the home page. Can a spider or bot store multiple versions of a webpage? Maybe the Vary header would help here?). 3. Redirect the user (or bot/spider) to the homepage, display the information based on the "section/contentid" part of the url. I'm not sure how you would do that. Is there a server var that can be relied upon that you can check to know where the user or bot was redirected from. 4. Use client side technology and location.replace to fix up the url so the user ends in the right place in the app, and has the standard one link type (with the #). Would something like that actually work? I'm sure I could make it work for a web browser, but I'm not sure what would work with search engine spider bots. Kevin N.
