从传统的ASP迁移 - ＆GT; ASP.NET超过六个月 - 战略会议？ [英] Migrate from Classic ASP -> ASP.NET over six months - strategy for session?

问题描述

我使用的是经典的ASP应用程序，使使用会话状态。它有相当多的网页。我慢慢迁移到.NET，约六个月ETA。

I'm using an ASP Classic app that makes use of session state. It's got quite a few pages. I'm slowly migrating to .NET, with an ETA of about six months.

是否值得改变在传统的ASP使用自定义的DB会话该时间框架的实现？或者我应该只是迁移这样的功能是应用程序之间独立，无会话共享？

Is it worth changing over the classic asp to use a custom DB session for an implementation of that time frame? Or should I just migrate so features are separate between the apps and no session is shared?

谢谢！

推荐答案

在过去，我已经通过维护两个应用程序，并通过在数据库层两者之间authenication信息转变。当用户请求访问新ASP.Net应用程式，写一个进入与GUID（S）和一个日期时间的表，然后重定向到认证页面，该检查表中的相应行，这是仅适用于一一定长度的时间（30秒），并有一个一次性使用。

In the past, I've transitioned by maintaining two apps, and passing authenication information between the two at the database layer. When the user requests access to the new ASP.Net app, write an entry into a table with guid(s) and a datetime, then redirect to an authentication page, which checks the table for the corresponding row, which is only valid for a certain length of time (30s), and has a one time use.

如果该行存在，同样的用户名进行登录，访问授权。

If the row exists, grants logged in access under the same username.

这篇关于从传统的ASP迁移 - ＆GT; ASP.NET超过六个月 - 战略会议？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！