This is a multi-part message in MIME format.
------=_NextPart_000_0005_01BFFD65.8594A9E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
We have a client who wants to set up kiosks so that customers will be =
able to order either from the kiosk or the WWW, same store and domain =
though. They want a login screen to only come up in the kiosks, this is =
where the kiosk administrator logs in so that he/she receives a =
commision for any sales from that kiosk.
I'm not too sure how to tackle this. Before I surround myself with a =
pile of research on "cookies", I was hoping for any insight at all, =
whether its real experience or a hypothetical design. Thanks for the =
input
------=_NextPart_000_0005_01BFFD65.8594A9E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>We have a client who wants to set up =
kiosks so that=20
customers will be able to order either from the kiosk or the WWW, same =
store and=20
domain though. They want a login screen to only come up in the =
kiosks,=20
this is where the kiosk administrator logs in so that he/she receives a=20
commision for any sales from that kiosk.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I'm not too sure how to tackle =
this. Before I=20
surround myself with a pile of research on "cookies", I was hoping for =
any=20
insight at all, whether its real experience or a hypothetical =
design. =20
Thanks for the input</FONT></DIV></BODY></HTML>
------=_NextPart_000_0005_01BFFD65.8594A9E0--
Comment