%%

%%

Evaxatropin

We've actually navigated into that iframe: I didn't just
load the same URL as that iframe in my main page.
It's really new. Basically a portal is an iframe, but you can tell the browser: make the thing in this iframe be
the main page. And that's not HTML History API trickery: the browser genuinely navigates into
the page which is inside that iframe. Don't trust the browser to do it, do it yourself.

But the key point here is: in between you creating the portal
and setting its src, and you activate()ing it, you've still got control.

You've got things like component reuse. In 2007 I gave a talk in London where I complained that people were writing links on their pages which look like this (a big
pile of JavaScript), a span, but "enhanced" with Ajax, loading
everything with Microsoft.XMLHTTP. I think the reason people started inventing
client-side frameworks is this: that you lose control
when you load another page. Instead of me letting the user click on a link that
then goes to the browser and the browser giving me back control when the new
page loads, what about implementing that myself?
Now, in the old days, when you clicked on a link, the browser went white and didn't show you
anything until the new page loaded.

Please let me know if you're looking for a writer for your weblog.
You have some really good articles and I think I would be a good
asset. If you ever want to take some of the load off, I'd absolutely
love to write some content for your blog in exchange for
a link back to mine. Please send me an email if interested.
Regards!

What's up, all is going fine here and ofcourse every one is sharing information, that's actually excellent, keep up writing.