How jCIFS Works #2 [was RE: [jcifs] jCIFS and Share name leng th?]

[Allen, Michael B (RSCH)]

> -----Original Message-----
> From:	rjw [SMTP:rob at wygand.com]
> Sent:	Thursday, November 15, 2001 9:11 PM
> To:	Allen, Michael B (RSCH)
> Cc:	jcifs at samba.org
> Subject:	Re: How jCIFS Works #2 [was RE: [jcifs] jCIFS and Share name length?]
> 
> Allen, Michael B (RSCH) wrote:
> 
> >>With the URL encoding/decoding fix I made, spaces work just great.
> > 	Well, the real issue is the '@' sign.
> 
> 
> Right, the spaces was a side effect of a bad fix for @'s. I've got both 
> working now.
> 
	Great!

> > 	Don't think headers. Protocols that use headers like http are telnet based protocols. CIFS
> > 	is a binary protocol. For example if you look at the document that describes the Remote
> > 	Access Protocol (RAP):
> 
> 
> When I said header I should have been more clear and said a flag in the 
> header. I was thinking that setting a bit in the flag or flag2 portion 
> of the header might do it.
> 
	Those are documented here:

	http://ubiqx.org/cifs/rfc-draft/draft-leach-cifs-v1-spec-02.html#s3.1.1

>  But, doesn't look that way... I was also 
> thinking that using an identifier other than "NT LM 0.12" might be the 
> trick, but looks that's a dead end as well.
> 
	http://ubiqx.org/cifs/rfc-draft/draft-leach-cifs-v1-spec-02.html#s4.1.1

	But you're right; it's not pertainent.