Hi,
Circuitsoft Development wrote:
> Why not? Almost every other daemon I've seen does.
that's not the point here. I don't want to have some more or less
unrelated registry entry to enforce a design decision for future versions.
regards
-- jochen
Why not? Almost every other daemon I've seen does.
Every http deamon I've seen support HTTP/0.9
Even Windows XP can share files with Windows for Workgroups
SMTP hasn't changed in years, and every extension I've seen to it (ex.
EMTP) is backwards-compatible.
Besides. It's not that complex a task,
On 2/17/07, Alex Austin wrote:
> Jochen,
>
> About TXT records:
>
> Looking at the SANE1 net protocol, the first RPC (SANE_NET_INIT) involves
> selecting a net protocol version. Couldn't SANEd 2 just use SANE1 protocol
> until the client asks for a different protocol version?
ahh- but now you req
Jochen,
About TXT records:
Looking at the SANE1 net protocol, the first RPC (SANE_NET_INIT) involves
selecting a net protocol version. Couldn't SANEd 2 just use SANE1 protocol
until the client asks for a different protocol version?
On 2/17/07, Jochen Eisinger wrote:
>
> Hi,
>
> Alex Austin wrot
Hi,
Alex Austin wrote:
> I'm working on a SANEd / WIA (Windows Imaging Architecture) bridge
> driver right now. I suppose I could be the contact person, but if
> someone else would prefer, I have no attachment to it. I figured the
> head maintainer of the SANE net backend could, but looking furthe
Jochen Eisinger wrote:
Hi,
>> The info I've collected so far:
>> Short name of protocol: sane-port
>> Long description: SANE Control Port
>> Name and Email of Responsible Party: Jochen Eisinger
>> mailto:joc...@penguin-breeder.org>> <- ???
>> Is this okay?
>> URL of Protocol Description:
Hi,
I've forwarded your mail to the sane mailing list. I'm not sure who
should be the contact person, so it's probably the best to discuss this
on the list.
regards
-- jochen
Alex Austin wrote:
> Jochen,
>
> I am working on building an integrated product which runs SANEd. When
> looking into wr
