Show Bid Request
Print Queue / Spooler custom app
Bid Request Id: 55831
|
|
|
|
Posted by: |
Jason Short (11 ratings)
(Software buyer rating 10 )
|
|
Non-action Ratio: |
Very Good - 12.50%
|
|
Posted: |
Apr 1, 2003
9:24:52 PM EDT
|
|
Bidding Closes: |
Apr 9, 2003
9:26:30 PM EDT
|
|
Viewed (by coders): |
74 times
|
|
Deadline: |
4/25/2003
TIME EXPIRED
|
|
|
|
|
Description:
Print Spooler
I am looking for the following application for a web café system.
Background:
When a user prints from the web café terminal the document should be spooled up (not printed). When the document is completely spooled (we know how many pages it will be) then the user should be prompted to accept or decline the printing of that document. If accepted then the document can be sent on to the real print spooler on the server.
Implementation:
Due to a very small amount of space on the web café machine themselves I would prefer to see this implemented as a print spooler on the server (where there is plenty of hard drive). The print spooler then needs to be able to talk to the client machine for confirmation of the job once it has spooled. I can do the client side system for the callback as the web café machine already has an application running in the system tray that this spooler could talk to over sockets or named pipes.
Operation:
In my mind the best scenario would be one where the server calls back to my client app and tells it how many pages are present. The client app asks the client, and if they approve it I send a message back authorizing the print job.
This may be complicated in the field by more than one printer present on the server (color and black and white). That needs to be taken into account as two print queues (I think). The client side app would then need to be given the information on the type of printer as well (color / bw) as the charges may be different.
Deliverables:
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Installation instructions on what the installer must perform. We will use our own installer.
3) Complete ownership and distribution copyrights to all work purchased.
4) Debugging and testing assistance to ensure project success.
Platform:
Windows XP Pro, or Windows 2000 Pro
Must be 100% finished and received by buyer on:
Apr 25, 2003 EDT
Deadline legal notes: All times are expressed in the time zone of the site EDT (UT - 5). If the buyer omitted a time, then the deadline is 11:59:59 PM EDT on the indicated date.
|
|
|
Bidding/Comments:
|
All monetary amounts on the site are in United States dollars.
Rent a Coder is a closed auction, so coders can only see their own bids and comments. Buyers can view every posting made on their bid requests. |
See all rejected bids (and all comments)
| Name |
Bid Amount
|
Date |
Coder Rating |
|
|
This bid was accepted by the buyer!
|
$650 (USD)
|
Apr 8, 2003
1:43:20 AM EDT
|
8
(Very Good)
|
|
|
Jason...
I already have custom client/server components that I have built using .NET. After reviewing your project, I built a test print server application and was able to receive data on my server from a workstation. The workstation was using a RAW printer port with an HP Color Laserjet 4500 device driver. The port is configured such that it sends the data directly to my Print Server application. My idea is pretty much in line with yours. Here's what I was thinking....
Workstations have two printers set up that that are directed to two RAW (non LPR) ports. When a user prints, it sends the data to the server, which saves the RAW print data to a file. The client then connects to the server, which recognizes the client (by IP or some other scheme) and display's a list of documents that are ready for print approval (there could possibly be more then 1 in the print queue. The user can then get a subtotal for charges based on how many pages are printed to what type of printer, and accept the charges. The server then sends the data to the appropriate printer queue, where it is printed. Files can be retained for easy spooling, or deleted upon completion/if not approved.
My client/server components are made in 100% managed Visual Basic .NET, and can handle multiple concurrent users.
If I start tomorrow (4/8/2003), I can have the first beta out to you by this Saturday at the latest (maybe even sooner). Like I said, I have already invested some time in the project. All I need to do is figure out the printer codes for a page break, and think out an application level protocol for client/server communications.
Hey, BTW, what OS is on the workstations, and how limited is the space? I could save you some time and make the client side app as well. Even if you don't use it, I can give you the code for it.
I have captured a screen shot of my current print server app in action. It is pretty simple looking right now, and most likely will be implemented as a service later. I have also attached a file that contains the RAW data for a test page. If I can get the printer makes/models you use, I can test with more precision.
I really want to express my sincere interest in this project. I don't have a job right now, and I would like to pay my rent this month (it is due on the 10th, but my Land Lord can give me until the 15th). I assure you I will be dedicated to this project until complete.
I look forward to hearing from you soon! Let's get this thing started!
Thanks,
Ryan Haney |
|
|
Attached File
|
|
|
|
|
|