>
> Can you define the operating systems, general scenario and use case, and
> goal you are trying to achieve?
>
I'm a BYU student, btw (but still hang onto this list because it's a good
one).
We want to have Windows lab (and possibly an OS X one) authenticate before
printing so that we can charge $0.03/page to their student account.
John walks into the Windows lab and sits down to check his e-mail.
He logs into the computer with his student id and password, which
authenticates against an LDAP server.
He opens a message from a professor with a homework assignment he wishes to
print out.
John sends his document to the print server using File -> Print, and selects
a print queue (which he thinks of as a printer)
The print client gathers information:
* Username
* Which printer (Color or B&W) is being printed to
* How many pages
* Price per page (or maybe determined by the printer type later on)
* Acceptance of the confirmation of the print action (and notifying of
the charge)
The print client then:
* Logs the data it has gathered, which will be csv imported into the
student charge program
* Sends the required actual data (postscript file?) which is put in the
queue
The print server prints the document
John picks up his document from the printer.
Or a slightly different (but seemingly more complex to implement approach):
John prints as per usual, but instead of asking credentials and printing
immediately, a touch-screen terminal awaits him at the printer
He sees his username next to a document title and selects it
After confirming his choice to print the document prints.
AJ ONeal
