Hi Phil,
ok, with your explanation, I don't see any use to removing it
or the other similar protocol identifiers that apply to IPP.
Thanks, Roger
On 11/28/2018 03:22 PM, Phil Race wrote:
The presence of this field doesn't do anything to suggest that
the JDK must support gopher protocol. It
The presence of this field doesn't do anything to suggest that
the JDK must support gopher protocol. It is an informational
attribute that may be returned by a remote print service to
say what schemes it supports. You can then "pick" one that
works for you to communicate with the remote print
Hi Phil,
On 11/28/2018 12:06 PM, Phil Race wrote:
> Please check in javax.print that the inclusion of the gopher
protocol is no longer needed.
In that case, 2d-dev is the list you want. Swing doesn't do printing.
Thanks for the correction.
It must have been a decade since I heard anyone
I am not understanding you. I thought the problem to be we got an array
of (say) 3 values
(ie printer names) returned from native where some or all of the
*values* were NULL.
And I am saying we should in such a case in the native code, before
returning,
remove from the returned array all
> Please check in javax.print that the inclusion of the gopher protocol
is no longer needed.
In that case, 2d-dev is the list you want. Swing doesn't do printing.
It must have been a decade since I heard anyone mention gopher, but did
you really mean to remove a Java SE public API variable ?
