hi Steve, I don't use FB, but that looks like custom browser history implementation thing, quite different from what is implmeented in iUI, most probably for using it in: - bookmark - automatic convertion from bookmark saved on iPhone (#home.php) to correct page redirect when viewed on different device in iUI you got history based on hashed, generated values which goes into array and then history is rebuild using items stored in array, with FB you got history implementation based on custom solution. I guess someone could send "hi, that's great link" from Iphone to other people and that should correctly work when viewed on more standard multipage FB implementation, I'm using GWT (Google web toolkit) for Ajax like apps and for example to provide custom navigation with nice, readable bookmarks: #index.html #examples/events/ #examples/animation/ #examples/widget/button/ such tokens are used for navigation and they are created from already existing page(s) (YUI library samples) converted into single-page ajax apps, where existing links are converted to history tokens, as mentioned that way of history implmenetation is not something you'll got out-of-the-box with iUI, however you can try different javascript implementation instead of iUI one,
from implementaiton point when you got history item: #profile.php?id=someID you simply split token into: - what: "profile" - who: someID and then take correct action in your application, this reasambles urls, but converted to #-hased ones for use in history navigation, regards, Peter On Jan 7, 5:16 pm, "Steve Finkelstein" <[EMAIL PROTECTED]> wrote: > Hi folks, > > Probably the most impressive application I've run into for the iPhone has to > be Facebook's implementation. I'm looking for ways to improve my application > to be as responsive as theirs. Unfortunately it has quite a way to go. Does > anyone know how this form of 'routing' works? > > For instance the home page for iphone.facebook.com looks something like: > > http://iphone.facebook.com/#home.php > > then if you click on profile it'll route you to something that looks like > > http://iphone.facebook.com/#profile.php?id=XXXX > > Is this actually 'leaving' the page and requesting profile.php? I'm > completely confused with the hash mark in front of the PHP file and the > mechanics behind this style. It seems to be extremely well implemented > though and I'd like to learn more about it. I'm having a ton of issues with > my application now where Ajax calls randomly do not get sent to the server. > I haven't figured out why, maybe mobile safari is caching request URLs. But > I'm looking to rebuild parts of the architecture to get it to work, and > would love to understand the mechanism being used above. > > Does anyone know what is going on with the browser and HTTP requests with > the methodology listed above? Any further reading? > > Thanks! > > - sf --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
