|
|
Posted by Jerim79 on 02/07/07 15:19
On Feb 6, 3:50 pm, Jerry Stuckle <jstuck...@attglobal.net> wrote:
> Jerim79 wrote:
> > I did try to find the answer to this before posting, so this isn't a
> > knee jerk reaction.
>
> > What I am trying to accomplish is to have a script that opens a
> >cookie, reads a value, and then use a switch/case to take action based
> > on that value in thecookie. I want to set thecookiemanually, so I
> > don't need setcookie(). I see that in PHP it stores thecookiein
> > memory. Is there a way to have PHP just read acookiefrom the desktop
> > machine? Does it have to set it first? Am I better off with Javascript
> > for this?
>
> > The situation is that we have 4 computers. We also have 4 different
> > types of specialty printers, each for a different function. We don't
> > know which computer will be hooked up to which printer, and they may
> > be switched out routinely. We are trying to develop a simple script
> > that reads the value of thecookiewhich tells it which printer to
> > print to and what to print. This way, we can easily switch computers
> > around as needed, and will only need to change the value in thecookie
> > to have it access the correct code so that it prints the correct
> > information in the correct format.
>
> You can use acookiefor this. But here's a suggestion - have a
> password-protected admin page which sets thecookie. When they move the
> computer, they have to log into the admin page and tell it which printer
> to use.
>
> This then sets thecookie, which is now available for the rest of your
> pages. Of course, you would want to ensure that cookies are not cleared
> when the browser shuts down - at least not for your site.
>
> --
> ==================
> Remove the "x" from my email address
> Jerry Stuckle
> JDS Computer Training Corp.
> jstuck...@attglobal.net
> ==================
I talked with my boss, and he is completely against the kiosk mode
(for whatever reason). Let's step back from the word cookie for a
minute.
We are going to have 4 "kiosk" style computers, each of which display
the same registration form on a remote server. As the customer fills
out the form, he may get redirected to other forms based on how he
answered (Multiple paths). The very last step for everyone, after
everything is filled out and the customer submits the form, we want to
have a small script on the server that accesses a file on the kiosk
computer. The script on the server will read the value and perform an
action based on that value.
Cookie is the word my boss threw out there. I don't see why it has to
be a cookie, if PHP can access a remote file on the "kiosk" machine
from the server. We don't want to pass the value with the URL, as he
would have to go back and change all the pages of the PHP form to
pickup the value and pass it along to the next page.
Navigation:
[Reply to this message]
|