
Thanks for the reply al. Here (in a nutshell) is what we have and what we
need:
1) Over the years, we developed an app for an Oil and Gas marketing company.
Essentially they sell gas pipeline data to such orgs as Communities, Cities
Governments etc. As a requirement of access to this data, it is important
that the visitor (ultimately the client login) is tracked at every step.
They first hit a Login Page (tracked) then they are sent to a Validation
Page (tracked), then ultimately to the Pricing/Buying/Selling areas,
2) During this login/validation process, they get a cookies (it contains IP,
reverse DNS lookup data and some other items that are hashed) at every step
(security requirements dictate that we must track every step for Government
Reporting purposes),
3) The user will have a random number of login attempts (from 2-5). They do
not ever know how many attempts they have. This changes every time a user
(new or existing session) hits the login or validate pages. This is in case
they use the Back/Forward buttons,
4) Once they have logged in, the data that is stored in cookie(s) is put into
a DB, the cookie(s) is/are recreated with garbage data, then removed.
So the end result we need (and was supposed to have been built) is the
following (this is for Management Purposes):
1) Good morning/afternoon etc Bob,
2) You have logged in: X times,
3) There have been: X Total logins.
We know that there is some asp on this site, becuase we populate the DB. We
also have an asp page the does retrieve the data from the db and generates a
very basic page with the above data. But we need it to be displayed in the
HTML page for the currenly logged in Management type.
Now the difficult part, the site uses HTML to render everything to the
client (no asp pages except for the db inserts/updates and as mentioned
above). One of the reasons is that some of our clients have remote sites
(Nunavit, Bahamas, Nigeria etc - pretty much anywhere). So we cannot dictate
what desktop technology they must use. In fact some still use Windows
98SE/ME (I.E. 5 in some cases), some use Linux deriviates, some use Macs
etc. Thus (I beleive) the reason for the site using all HTML pages with no
scripting tech except where absolutely required.
I am thinking (from what I am finding) that this is probably not possible
without using the code in ASP/PHP pages etc. The powers that be in the white
towers are old school at it is going to take time to convince them that
newer technologies are better suited to what we need, but alas that will
take time and we still have to remember the client side technologies
available.
Sorry for rambling, but I am trying to give everyone as best a picture of
what is required without (hopefully) plugging this up with tons of posts.
Thanks again,
Marian