Validate my approach for sharing “session” between Classic ASP and .NET webservices

Question

I have a Classic ASP system that's going to invoke various .NET webservices that produce reports. Clearly the session can't be shared between them, so instead of trying to shim a session module in SQL server, I thought instead about creating "tokens" for reports - ie a one-time use key that could be passed upon invocation from the ASP page via Ajax that would create the report and expire the key.

Are there any tricky things I should be aware of? Am I making this too simple? Or too complicated? They're all on the same IIS on Windows 2k3 Server

Answer 1

Your solution is a reasonable one. Its pretty simple to implement (a GUID that is stored in a SQL table along with a timeout value). I've used this approach myself in a number of places.