Another way would be sending a fax but I suppose that takes more time
to setup and can go wrong easier then having a page open that
automatically refreshes or sending an email. So yes your right. The
only thing I would remove is the Ip restriction cause in case their IP
changes the site has to be
When you get a new order, new row in database table appears. Set it's
confirmed = 0 and when staff refreshes the page (or JS does that every
minute) they would see the new order. As for IP restriction - why would you
want this? Cake's got it's auth, so there's no need to add IP restriction.
As
Thanks for the replies. The IP restriction was since the employees
know (or probably find out) the password. They don't want a situation
where they fire somebody and they have to worry about that person
logging in from home and messing with orders. The IP restriction would
be an extra layer of
Create each employee a different user and log which orders did the employee
see.
Then, after firing a employee you will only have to delete his/her user.
Simple as that.
Faifas
On Wed, Sep 16, 2009 at 14:48, Tim t...@gurske.com wrote:
Thanks for the replies. The IP restriction was since the
I think Tim is right here. Individual logins work in theory but in a
busy restaurant where supposedly a single computer will be logged in
all day and used by everyone... passwords would get swapped, written
on a post-it and other secure things in a heartbeat. Security =
putting the post-it under
Thanks Martin - I love that ajax poll idea. It also does what Aivaras
suggested to keep the session alive.
Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
CakePHP group.
To post to this group, send email to
Hey,
I am developing a website for a local delivery place that will feature
online ordering. I am competent enough to build the ordering part of
the site but I did have one question for more developed programmers:
I need a way for the restaurant to know immediately when someone
places an order.
