Haha - looks like you beat me too by 5 min Jordan ;) On Thu, Sep 18, 2008 at 12:38 PM, Jordan Knight <[EMAIL PROTECTED]>wrote:
> Sorry Ross J - not Michael. > > > > Regards, > > *Jordan Knight* > Readify - Senior Developer > > Suite 206 Nolan Tower | 29 Rakaia Way | Docklands | VIC 3008 | Australia > M: +61 403 532 404 | E: [EMAIL PROTECTED] | W: www.readify.net > > > > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *Jordan Knight > *Sent:* Thursday, 18 September 2008 12:35 PM > *To:* [email protected] > *Subject:* RE: [OzSilverlight] A couple of questions > > > > Hi Michael, > > > > I can answer 1 and 3 for you (and maybe a bit of 4): > > > > The short answer is Forms Authentication and/or ASP.NET membership – i.e. > use the normal stuff J. Whenever Silverlight accesses the server, it uses > the standard browser networking stack, so you will have access to session > state, cookies and all the other goodies you expect. > > > > To find out which user is logged in you can use the ASP.NET Authentication > Application Service, which can be exposed via WCF quite easily (then you can > log in and check login status etc from Silverlight). > > > > 4 is a little more tricky, but basically you could hook up events to AJAX > changes in the page then fire through pieces of information to Silverlight > using the HTML JavaScript bridge... It's quite easy to do, have a Google > around. > > Regards, > > *Jordan Knight* > Readify - Senior Developer > > Suite 206 Nolan Tower | 29 Rakaia Way | Docklands | VIC 3008 | Australia > M: +61 403 532 404 | E: [EMAIL PROTECTED] | W: www.readify.net > > > > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *Ross McKinnon > *Sent:* Thursday, 18 September 2008 12:20 PM > *To:* [email protected] > *Subject:* [OzSilverlight] A couple of questions > > > > Hi all, > > > > I am the CIO of Michael Hill Jeweller which is an international (US, > Canada, New Zealand, Australia) jewellery retail chain whose global head > office is based in Brisbane and we are in the process of replacing our > global website. The executive here are very excited by the opportunities > presented by silverlight and we will be developing the new site using this > technology and are trying to release it as soon as possible. > > > > I did have a couple of questions which I have posed to Microsoft, but they > have been unable to answer and most of them are directed towards my > personally perceived weaknesses of silverlight and I was hoping that someone > would be able to point out how they can be achieved. Hopefully our work > arounds are not the suggested best practice. > > 1) What is the best way of persisting user identity through multiple > silverlight pages? > > 2) It appears to me that linq to SQL entities seem to lose the ability to > maintain state (ie know what is changed) after passing through a wcf call > and silverlight treats it like a normal class. Is that the case and if so, > is that going to be changed? > > 3) What is the best practice for integrating security and sessions between > asp.net / silverlight / wcf? > > 4) Are there plans for a binary formatter in the silverlight framework? > > 5) I have been overlaying silverlight pages over aspx with master and > content pages. The largest issue with that is being able to pass information > between your master and content pages (easily achievable in aspx), but are > there any plans to implement a method to easily pass information between SL > pages on the client (usually user specific information), other than at > creation of the page. > > Thanks for any help in advance, > > Ross. > > 18/9/2008 Ross McKinnon [email protected] > > This email and any attachments ("Email") are intended only for the > addressee > and may contain privileged, confidential and/or disclosure-exempt > information. > You must not edit this Email without our express consent. > Michael Hill Jeweller (Australia) Pty Ltd does not warrant that this Email > is complete, error-free or virus free, and by opening any attachments, > you accept full responsibility for the consequences. If you are not the > addressee, > you must not disseminate, rely upon or copy this Email, and you must > immediately > erase permanently and destroy all records of it and notify us by phone (at > our cost). > Thank you. > > ------------------------------------------------------------------- > OzSilverlight.com - to unsubscribe from this list, send a message back to > the list with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > ------------------------------------------------------------------- > OzSilverlight.com - to unsubscribe from this list, send a message back to > the list with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > ------------------------------------------------------------------- > OzSilverlight.com - to unsubscribe from this list, send a message back to > the list with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > ------------------------------------------------------------------- OzSilverlight.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net
