Access to SMS and browser content tombstoning

WP7 newbie here..

In my application, I am using embedded web browser control to load an external web page.

I have a PIN based validation step in that application, which involves

1) User Leaving the current application, (which has a external web page loaded in the embedded web browser) to launch the SMS Inbox.

2) User reads the SMS he just received, which has the PIN. I am sending this SMS to the user.

3) The User then needs to resume back to the original application by hitting back button, to enter the PIN which he received in the SMS earlier.

Once user enters Step2, my application will go into background, and subsequently will get tombstoned. Once user enter Step3, I want to restore application state (with the embedded web browser control), without making a fresh HTTP request again to load the web page.

So, with the given scenario in my mind, I have following two questions -

1) Is there a better way to do all this, like not having to exit the original application, and still let user read the SMS. ( i.e any api to read sms ?)

2) Is there a way to serialize the browser state/save entire web page (with images, css, js) , such that entire web page can be rendered exactly the way it was, when user left the running application.

Important points:

1) I can only use SMS as a communication channel. I c开发者_开发技巧an not use something like raw push notification channel, which could let me show PIN to the user, without exiting the application.

2) I am targeting Windows phone 7.0 runtime, but if there is a better option available in Windows Mango update, please do tell me.

Any sort of help is greatly appreciated.

Update: Added link to the embedded web browser component.

1) There is no API that would let you access the contents of the Messaging hub from inside your application. This is set up for privacy purposes.

2) By default, the web browser saves its state. So if you navigate away from your app, and then come back - the same web page will still be there unless you explicitly re-navigate on activation

1) The better way to do this would be to not embed the web page within an app. Just build a mobile website. If all the functionality is within the web page you gain nothing but problems by trying to put it inside an app.

The web browser control is not intended to be used to create an alternative browser (which is really what you're doing).

2) You can try using the SaveToString() method to store the state of the page when tombstoned but this doesn't allow for modifications to the page since it was loaded (including anything dynamically updated or any state in javascript). If you have multiple pages you'll also need to maintain the internal backstack and the state of each page separately.

Short answer: If you want to put your application logic in a webBrowser control then you can't support tombstoning. Fast-App-Switching (in Mango) partially addresses this but not completely.