[WinPrnDev] Re: Creating a Printer Driver
- From: Sam Elamin <hussam_88@xxxxxxxxxxx>
- To: <winprndev@xxxxxxxxxxxxx>
- Date: Thu, 25 Mar 2010 12:16:58 +0000
Rune
I think I am beginning to understand what your saying, but you see the solution
is to be used alongside a print management solution, so any document send to
the print server will initially be paused till secure release by the end user.
This soluion will most probably be implemented on a students laptop and if you
go down your route first time set-up will be a massive pain which would most
probably put end users off.
If I go with Abduls solution of extracting the EMF using a pre-installed print
driver, from an end-users prospective all they will see is an installation
routine that will create the printer with the driver which will automatically
have all the settings needed to send the document to the print server.
Although far too much work, you can clearly see why the EMF extracting print
driver is a far more elegant proposition.
RegardsSan
> Date: Thu, 25 Mar 2010 12:46:13 +0100
> Subject: [WinPrnDev] Re: Creating a Printer Driver
> From: jjflash@xxxxxxxxx
> To: winprndev@xxxxxxxxxxxxx
>
> On Thu, Mar 25, 2010 at 10:32 AM, Sam Elamin <hussam_88@xxxxxxxxxxx> wrote:
> > Thanks for your email, what I am trying to do is to print wirelessly across
> > networks, and I figured if I create a print driver that works as an
> > application then that would be the best option, but it seems getting the
> > path of a document is virutally impossible so whats the best way to get a
> > document printed via a printer on a client side and have that document
> > released on a print server which is a part of a different network
>
> I am going to bite one more time. There are too many custom-developed
> solutions in the world already.
>
> The word "wirelessly" is redundant. Whether a user is using wi-fi or
> an ethernet cable is often transparent to the user. Shared resources
> are still accessible given a normal network configuration.
>
> The "different network" requirement is why you're about to spend lots
> of time on something that has already been solved. You are trying to
> do the job of the network admin while wearing your developer hat.
> You're thinking like a developer rather than simply ask the network
> admin the obvious question: "Why?".
>
> Sending a document from A to B is only a small part of the equation.
> Have you considered DOS attacks? You could easily end up in a
> situation where someone in Japan has depleted your paper supply
> through the use of your software. The rainforrest will disappear.
>
> If the network is open, then sharing a printer is _very_ easy. The
> problem arises when network A have to trust network B. Once you solve
> that problem (and it is a big one), you might discover that you can
> use off-the-shelf software and end up with a more secure solution. (A
> VPN client is a very obvious choice for the scenario you describe)
>
> If your network admin is a nit, you still have to co-operate with
> him/her to install your server software on the inside of the victim's
> network.
>
> --
> Rune
> ---
> Questions? First check the UndocPrint pages at
> http://www.undocprint.org/winspool
>
> To unsubscribe, visit the List Server page at
> //www.freelists.org/list/winprndev
_________________________________________________________________
Do you have a story that started on Hotmail? Tell us now
http://clk.atdmt.com/UKM/go/195013117/direct/01/
Other related posts:
