To store or send component data I use XML format.
Why not using a simple INI file for storage ?
For large data, it can simply be mapped into a SQL table.
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing
I ment I will remove the XML support (probably).
The component is designed as an 'in memory' account/user database capable
to authenticate users and to store the account data (actually to binary
file,
or to an XML file optionaly).
Then you can simply create a component containing the
To store or send component data I use XML format.
Why not using a simple INI file for storage ?
For large data, it can simply be mapped into a SQL table.
Current state is..
A base component w/o any storage methods.
From that base I derived two more components,
one that writes binary to a
On 02-Dec-05 11:16:33 Arno Garrels wrote:
Maurizio Lotauro wrote:
On 30-Nov-05 08:19:53 Arno Garrels wrote:
Maurizio Lotauro wrote:
[...]
Will they contains passwords?
Yes, with an option to save the MD5-hash only.
What is the purpose of the component?
The target is server only or
Maurizio Lotauro wrote:
On 02-Dec-05 11:16:33 Arno Garrels wrote:
Maurizio Lotauro wrote:
On 30-Nov-05 08:19:53 Arno Garrels wrote:
Maurizio Lotauro wrote:
[...]
Will they contains passwords?
Yes, with an option to save the MD5-hash only.
What is the purpose of the component?
Maurizio Lotauro wrote:
On 30-Nov-05 08:19:53 Arno Garrels wrote:
Maurizio Lotauro wrote:
[...]
Will they contains passwords?
Yes, with an option to save the MD5-hash only.
What is the purpose of the component?
The target is server only or client too?
I made it to manage user
Arno Garrels a écrit :
I ment I will remove the XML support (probably).
The component is designed as an 'in memory' account/user database capable
to authenticate users and to store the account data (actually to binary file,
or to an XML file optionaly). I need such a simple component for a
Guillaume MAISON wrote:
Arno Garrels a écrit :
I ment I will remove the XML support (probably).
The component is designed as an 'in memory' account/user database capable
to authenticate users and to store the account data (actually to binary
file, or to an XML file optionaly). I need such a
Arno Garrels a écrit :
In fact, the pattern would be to have your accounts manager ignoring
everything on how to store itself and having some classes that connect
to it, knowing how to handle it to store and/or retrieve its data.
not sure to have been clear enough, but... ;)
So I guess the
On 30-Nov-05 08:19:53 Arno Garrels wrote:
Maurizio Lotauro wrote:
[...]
Will they contains passwords?
Yes, with an option to save the MD5-hash only.
What is the purpose of the component?
The target is server only or client too?
[...]
Are there alternatives?
Why don't use the streaming
On 28-Nov-05 09:21:48 Arno Garrels wrote:
Hello,
I'm actually writing a simple user manager component that I would like
to contribute to ICS. The component makes use of classes
TCollection/TCollectionItem to realize a tree-structure. A user group
contains accounts, accounts may have parameters.
Maurizio Lotauro wrote:
On 28-Nov-05 09:21:48 Arno Garrels wrote:
Hello,
I'm actually writing a simple user manager component that I would like
to contribute to ICS. The component makes use of classes
TCollection/TCollectionItem to realize a tree-structure. A user group
contains
To store or send component data I use XML format.
XML-text is written without the help of a third party component
however
for parsing I use Stefan Heymann's TXmlScanner/TXmlParser
http://www.destructor.de. It appears to be the freeware solution with
less overhead. Should I better avoid use
Angus Robertson - Magenta Systems Ltd wrote:
To store or send component data I use XML format.
XML-text is written without the help of a third party component
however
for parsing I use Stefan Heymann's TXmlScanner/TXmlParser
http://www.destructor.de. It appears to be the freeware solution
14 matches
Mail list logo