1,弹出框的报错与实际的错误命名不统一
2,弹出框格式与其他模块的不一样格式，包括里面的unit layout
3,展开下拉框的显示内容跟数量和需求设计的不一样
4.最近遇到一个问题
要求通过系统A直接登录系统B
测试功能实现同时还要考虑权限负向的问题
如果没有权限，A是不可以直接跳转到B系统
当不给B权限登录A的话，A是看不到跳转到B的入口
最近测试遇到2个问题
1）通过登录和登出，可以使权限立刻生效
2）无痕浏览器连续刷新2次才能生效刚才的设置或者等2分钟
这里前端设置的session时间是1分钟，后台服务器在DB更新是2分钟一次，就产生了生效的时差
重启IIS依旧有问题
开发小姐姐洪荒之力费尽脑汁了好几天，最后开发小哥帮忙拨开迷雾
what-is-the-difference-between-iisreset-recycle-refresh-and-restart？
In IIS7, there are numerous things you can do that seem to restart the website. I am unclear about exactly how they are all related.
- run iisreset from the command line
- refresh a website
- recycle an app pool
- restart a website
Can someone explain exactly what each one does please?
iisreset will stop and start the World Wide Web Publishing Service. This, of course, applies to all of your application pools. I'm sure you noticed a process being created for each application pool. This process will handle requests for all websites associated with it. When you recycle an application pool, IIS will create a new process (keeping the old one) to serve requests. Then it tries to move all requests on the new process. After a timeout the old process will be killed automatically. You usually recycle your application pool to get rid of leaked memory (you might have a problem in your application if this needs to be a regular operation, even though it is recommended to have a scheduled recycle). As for restarting a website, it just stops and restarts serving requests for that particular website. It will continue to serve other websites on the same app pool with no interruptions.
If you have a session oriented application, all of the above will cause loss of session objects.
Refreshing a website has no effect on the service/process/website and is merely a UI command to refresh the treeview (maybe you added a directory you don't see in the management console).
- Refresh a websites just reloads data from the server
- Restart a website doesn't do much really. By stopping the web site, it will no longer listen for requests on any of it's bindings. Starting it again makes it start listening again. Processes serving the web site remain unaffected.
-
iisreset stops and starts the whole webserver. That's everything - all your users lose their connections while this is happening.
Recycling an application pool stops and started the processes associated with the application(s) that are in that pool. Strictly speaking, it doesn't have anything to do with the website (except for the active content from those applications.)