On Thu, Mar 8, 2012 at 7:19 PM, Jef Spaleta <jspaleta(a)gmail.com> wrote:
1) What if I've hopped networks since then and the print job that
was
que'd was on a printer that was only visible on the original network?
2) What if I've hopped networks and the old network and the new
network have a printer at the same 192.168.x.x address but are
physically different printers?
The lazy answer to both is "fail, or not, the same way as cups
currently fails, or not" (in fact, could the session printing service
simply be cups that treats the system instance as another remote
server?).
Ideally, I suppose, we would need a concept of "network identity", at
least for wireless networks (where NetworkManager already can
distinguish between networks) and perhaps even for wired networks
(where at least Windows 7 tries to distinguish between them, and in
some cases fails quite visibly).
Mirek