| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 83.1 | I don't think a persistent client is needed | HANNAH::HASTINGS | Tom Hastings, DECprint Arch. | Tue Apr 28 1992 15:50 | 154 |
| 83.2 | comparison to a similar system | DECWET::LAURUNE | Bill Laurune, DECwest Engineering | Wed Apr 29 1992 16:01 | 8 |
| 83.3 | Need to be able to list ALL print jobs of a user, no matter which server they went to | HANNAH::HASTINGS | Tom Hastings, DECprint Arch. | Fri May 01 1992 10:05 | 19 |
| 83.4 | A delete-after "viewing" option might be better than "printing" | HANNAH::HASTINGS | Tom Hastings, DECprint Arch. | Fri May 01 1992 11:52 | 19 |
| 83.5 | How a non-persistent client can get new attribute-value OIDs | HANNAH::HASTINGS | Tom Hastings, DECprint Arch. | Fri May 01 1992 11:53 | 55 |
| 83.6 | Reason for a persistent client: reliable push document after crash | HANNAH::HASTINGS | Tom Hastings, DECprint Arch. | Wed Sep 02 1992 10:12 | 35 |
| 83.7 | Persistent Client: I'm for it. | DECWET::GREGORY | Quick what is 93**7? | Wed Sep 02 1992 14:22 | 10 |
| 83.8 | Persistence as value added option? | HANNAH::SMITH | Michael J. Smith: DSG1-1/K8 | Thu Sep 03 1992 04:14 | 19 |
| 83.9 | Value Added - NOT! | DECWET::GREGORY | Quick what is 93**7? | Thu Sep 03 1992 17:11 | 12 |
| 83.10 | Whats involved in a persisten client? If too much for V1, save for later | HANNAH::HASTINGS | Tom Hastings, DECprint Arch. | Tue Oct 06 1992 13:40 | 47
|