lol :) Sorry, I'll pack-up my paint brushes and drive my VW Beattle car back to my soho cafe and sip latte's wearing a French Beret..
>From memory WCF RIA Services team owns the Navigation framework so all rounds will point to them for this kind of thing when it comes to SL. --- Regards, Scott Barnes http://www.riagenic.com On Mon, May 16, 2011 at 11:11 AM, Jordan Knight <jak...@gmail.com> wrote: > Pipe down designer boy :p j/k > > WCF Ria services also has a cool auth bit in it. > > Cheers, > > Jordan. > > On 16/05/2011, at 11:02 AM, Scott Barnes <scott.bar...@gmail.com> wrote: > > Now for your next trip (hehehe) is to handle transition + bookmarking > that accommodates security authentication. Overall problem with Deep Linking > as a concept is that there is a series of entry points that need to be > upheld but also guiding the user through this (kind of like a fast-forward > button like experience) is what often gets lost. A website by itself is > different as its some what flat and document centric. Dynamic content plays > by a different set of rules... > > I mention this as i remember listening to why MTV moved from 100% flash to > hybrid and later to inverse hybrid and a lot of what was found was due to > the site being top-heavy but also the deep linking model was somewhat broken > because it was the small subtle xp points that got lost along the way. > > That being said check out Mach-II for Coldfusion David, it's something you > could also draw some inspiration from around > filter/plugin/listener marshaling using a XML structure like the one you've > outlined. > --- > Regards, > Scott Barnes > <http://www.riagenic.com>http://www.riagenic.com > > > On Mon, May 16, 2011 at 10:54 AM, David Burela < <david.bur...@gmail.com> > david.bur...@gmail.com> wrote: > >> I found a way to easily secure any Silverlight application (that is using >> the Navigation framework), and thought I would share it with the list. >> To secure your application you only need to put around 15 lines of xaml >> into MainPage.xaml >> The syntax is similar to the page authorisation config in an >> ASP.Netapplication >> >> <authLoader:NavigationAuthRule Uri="/Views/CustomerPage.xaml"> >> <authLoader:Deny Users="?" /> >> <authLoader:Allow Users="*" /> >> </authLoader:NavigationAuthRule> >> >> >> <http://www.davidpoll.com/2010/01/01/opening-up-silverlight-4-navigation-authenticationauthorization-in-an-inavigationcontentloader/> >> http://www.davidpoll.com/2010/01/01/opening-up-silverlight-4-navigation-authenticationauthorization-in-an-inavigationcontentloader/ >> >> There are two controls: >> *AuthContentLoade*r will check that the user is allowed to access the >> page. If they aren't then an UnauthorizedAccessException is thrown. >> To catch this the AuthContentLoader control is wrapped in a * >> ErrorPageLoader* control. This is configured to catch the Unauthorized >> exception and can redirect to a login screen >> >> Hope it helps someone >> -David Burela >> >> _______________________________________________ >> ozsilverlight mailing list >> <ozsilverlight@ozsilverlight.com>ozsilverlight@ozsilverlight.com >> <http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight> >> http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight >> >> > _______________________________________________ > ozsilverlight mailing list > ozsilverlight@ozsilverlight.com > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > > > _______________________________________________ > ozsilverlight mailing list > ozsilverlight@ozsilverlight.com > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > >
_______________________________________________ ozsilverlight mailing list ozsilverlight@ozsilverlight.com http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
