Well, I don't get it. To avoid data collision all that is required is
for the application to generate a unique ID, that could be saved on the
device. I doubt that any of these uses, that you mention, require that
the hardward be unique. Only that the application be able to generate
a unique ID so that there are no data collisions, as you put it.
This can be done without a unique h/w id.
On Wed, 8 Aug 2001, George Aslanis
wrote:
> Unique ids are a requirement in the business world especially data
> collection environments for several reasons. I've noticed too many of these
> threads assume a one-to-one relationship between point of acquisition and
> the end-user where a pseudo unique user name may suffice. In almost all
> facets of business a multi-user server based model is prevalent.
> Environments such as warehouse, hospitals, restaurants, distribution
> centers, etc., require transactions to be uniquely identified to avoid data
> collision. Also software development companies use unique ids to control
> client-server software pricing in regard to number of units supported in a
> particular pricing tier. Without the use of a descent security algorithm,
> PDA's without a unique serial number can not be used in this environment.
>
> "Michael S. Davis" <[EMAIL PROTECTED]> wrote in message
> news:59248@palm-dev-forum...
> >
> > On Wed, 8 Aug 2001, Richard Burmeister wrote:
> >
> > > > From: manish jaggi
> > > >
> > > > ... i have a problem . The hot sync username may be same .
> > > > The applications doveloped by Mr Ardiri like Dkjr or phire
> > > > display a unique number on the registration screen that
> > > > is unique for the device and many other applications like
> > > > chess from chessgenius do the same.
> > > > I just want to know how to get that value.
> > >
> > > There simply is no guaranteed unique identifier on all Palm OS devices.
> You
> > > can use the HotSync name, the serial number (on flashable devices) or
> > > anything else you want to use (e.g. time of installation, the owner name
> in
> > > the prefs db, etc.) and you can combine these pieces of information in
> any
> > > way you want to create a relatively unique number. I doubt that people
> who
> > > have done this in their own apps want to share the exact details with
> > > anybody else, but this is a strategy you can use.
> >
> > I guess I wonder why it has to be unique, in the first place.
> >
> > Even if the user name was John Smith, how many of those do you think will
> > try to use the application. And they still need the code. So, what if
> > there are more than one.
> >
> > In all the registrations I have seen, I have almost always (99.99% of
> > the time) seen the Hot Sync name be something related to the user. I mean
> I
> > have never seen something like John Doe trying to submit a user name of
> > Jack Jones. And if the .01% were using the same name to cheat me out of
> > a registration, it's down in the noise.
> >
> > I wouldn't worry about trying to develope something that depended on an
> > absolutely unique id. 1) It's not worth the effort and 2) If the app is
> > that desireable that it seems justified to spend the time, it will just
> > be cracked and you'll lose more that way anyway.
> >
> > So why bother?
> >
> >
> >
> >
>
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe, please see
>http://www.palmos.com/dev/tech/support/forums/
>
----------------------------------------------------
Shoot-to-Win
Protect the 2nd Amendment
----------------------------------------------------
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
