Disclaimer: This is my experience as developer, not as a DBA.
I'm a fan of mirroring, but so far my experience with log shipping for any purpose other than backup/recovery leaves an awful lot to be desired.
About 6 months back our Corp IT dept implemented a "reporting server" that is updated every 1/2 hour via log shipping.
The original intent was that this server would be used for both standardized ERP system reporting and ad Hoc reporting done via query software (IEV) or MS Access.
Out of every hour, we lose 10 minutes of connect time (5+5) while the shipped logs are being posted to the databases. Existing connections are completely blown away, including tests I ran running an Express Server SQL Query to a DB on a linked server.
As the databases are apparently thrown into recovery mode during the log posting process, I now understand why this happens.
However, an undesireable consequence is I have to carefully schedule any reporting, to ensure it does not start or end during a blackout period.
Not sure how this will play in Podunk IF they ever try to push the regular users into using this server for reporting. I suspect the first issue will be the blown connections, rapidly followed by "I just did a transaction but it's not showing in my report."
At the very least the broken connection issue has to be fixed for users to accept running a reporting server this way.