[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Auth]simplest logon design proposal

From: Jeremy Petzold
Subject: Re: [Auth]simplest logon design proposal
Date: Wed, 25 Jul 2001 08:56:47 -0700 (PDT)

that would be the auto fill system, however it is
difficlt to do that is a standard does not exist.
also, it would be nearly impossable to be able to
develope a system around such a lose protocol. having
standard fields and field names will allow us to tell
the deamon to look for feild tages, read what is
required and get the information from the Databank,
this can all be done automaticly with only a
conformation click from the user to send the data. if
we let web page designers make up any name they want
for certain fields we would not be able to provide
such a seemless system, and the database would have to
store repeat information that is tied to a spesific
site. to me that would be a big waste of space and
would make the system bloated and slow after a while.
the best way to go is to have a sigle standard and one
entry of information in a databank.

--- meson <address@hidden> wrote:
> Why restrict the information to a set of standard
> information fields? Why not allow ANY information
> required by the server to be stored? Here is how:
> The user goes to the web page where the information
> is to be entered. The web page contains XML tags
> that define the names of the fields that are to be
> provided to the server. E.g. as <INFO1/> or <INFO2>
> </INFO2>. How to provide the information is
> represented by HTML objects like an edit box, check
> box etc. The dotGNU system is integrated with the
> browser and reads what the user types in each field
> and stores it. It is then the responsibility of the
> dotGNU system to provide this information whenever
> the user returns to the web page.
> Amir Ahmed Ansari

Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger

reply via email to

[Prev in Thread] Current Thread [Next in Thread]