Call me crazy, but how are you expecting to access the printer from your server without the client having to approve anything?
Something on their side will have to talk to the printer and it isn't you're node application...
Call me crazy, but how are you expecting to access the printer from your server without the client having to approve anything?
Something on their side will have to talk to the printer and it isn't you're node application...
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
Call me crazy, but how are you expecting to access the printer from your server without the client having to approve anything?
Something on their side will have to talk to the printer and it isn't you're node application...
--
Yes desktop apps can a access the printer connected to the computer running it... In this case it would be the browser doing the printing.... Not a remote Web server/application aka node
That will work as long as the printer is a network shared printer, and is available to the server running node. Since this is replacing a VB.net app, that is more likely, but not assured.Mark
But from a web app, this is just pretty much exactly wrong. Let the
user have a print dialog. It's ok.
However, just to explore what I *think* is the thing you're trying to do, let's assume a few things about this _hypothetical_ server app you're talking about:
1. The user, for some reason, either already knows about and expects this print job, or will never see it or care about its existence.
2. You have a way to determine what user is triggering the report (perhaps with a username, login creds, or whatnot).
3. You can match the user to the printer(s) associated with them. JSON files might be a good, simple way to store this info.
4. The server running node has access to the same network/printers that the user triggering the report does.
If all of the above are true, you could use node to grab the printer name associated with the user triggering the report and have it execute a local print job to the same printer the user has as a "default" printer, provided that you kept the data store that has the key/value pair up to date (otherwise you'd be printing to an out-of-date "default" printer). You'd need to pass the user creds to the server, and have the printers installed on the server, obviously.
It's worth it, I think, to do some strong consideration about the end-user experience; simpler is almost always better, and don't make the user think.
I hope this helps point you in the right direction, and good luck!
-Skyler