|
Chris Britton of Unisys goes back to basics.
Why oh why EAI? - Part 2 | Part 1
Read Part 1
Security in the old system may be based on terminal ID and use the assumption that the end user is logged on for a considerable length of time. Both these assumptions are false in the web. Session control is particularly problematical when handling failures. For instance, suppose a new large web form corresponds to five old transmissions: how do you handle the situation where the third in the series fails?
A better approach is to take this code out of the back-end services rather than try and reverse the effects of the existing code. If you have extracted this logic, what you are left with are the core transaction and data inquiry code and this, with an appropriate interface, forms the service interface.
Read the rest of this article...
If you are not registered with the site, please register now to read the rest of this page.
If you are registered, please sign in to read the rest of this page.
Consultants' Advisory 2001
Copyright © 2001 |
 |
| 
