| 1 |
> > I'm currently processing orders one by one and I'd like to increase |
| 2 |
> > automation. I'm currently submitting an order number from my |
| 3 |
> > desktop to my server via firefox, and manually opening and printing |
| 4 |
> > the resultant receipt and shipping label. How would you guys |
| 5 |
> > suggest I set this up to batch so that I can process all orders |
| 6 |
> > with one click and have the resultant receipts and shipping labels |
| 7 |
> > print |
| 8 |
> > automatically, all at once? The printing part is what I'm having |
| 9 |
> > difficulty conceptualizing because I do all of my programming on |
| 10 |
> > the server side and the printing needs to happen on the client |
| 11 |
> > side. Not sure how to get those two working together. Both |
| 12 |
> > systems run Gentoo. |
| 13 |
> |
| 14 |
> Printing always on the same client? That's easy. CUPS can print over |
| 15 |
> the network. Configure a queue for that client on the server. |
| 16 |
|
| 17 |
Yeah, always on the same client. So I would set up cups on the remote |
| 18 |
server and fill up its queue with files to be printed, and set my |
| 19 |
local Gentoo firewall/printserver to monitor the server's cups queue? |
| 20 |
|
| 21 |
Could I instead have the server do something like 'lpr my.ip.address:631'? |
| 22 |
|
| 23 |
- Grant |
| 24 |
|
| 25 |
|
| 26 |
> If printing is supposed to happen on a variety of clients, that's a |
| 27 |
> wee bit more complex. Configure a queue for each client. Now you must |
| 28 |
> use some middleware (cgi, php, ...) on the server that figures out |
| 29 |
> from which client (IP) the request has come. Use the appropriate |
| 30 |
> queue. Shouldn't be too difficult. |
| 31 |
> |
| 32 |
> Uwe |
| 33 |
-- |
| 34 |
gentoo-user@l.g.o mailing list |
Archives