[jcifs] jCifs writing to Mailslots

[Allen, Michael B (RSCH)]

Mmm, yeah. Unfortunately it's just API documentation which isn't that useful at this
point. Looking at a quick capture it appears as though there is no session setup or tree
connect at all. It's just an NBT session establishment message followed by a minimal
SMB the format of the actual payload is as trivial as described below. This would require
modifying the jcifs.smb files although it would not be difficult. The question is, why
would one want to use this? It's a neat trick but it's not reliable. Does W2K or XP still
support these messages?

Mike

> -----Original Message-----
> From:	Christopher R. Hertel [SMTP:crh at ubiqx.mn.org]
> Sent:	Tuesday, June 10, 2003 1:19 AM
> To:	Allen, Michael B (RSCH)
> Cc:	'Sascha Teifke'; jcifs at lists.samba.org
> Subject:	Re: [jcifs] jCifs writing to Mailslots
> 
> "Allen, Michael B (RSCH)" wrote:
> > 
> > > -----Original Message-----
> > > From: Sascha Teifke [SMTP:sascha at teifke.de]
> > >
> > >       FileOutputStream fos = new FileOutputStream( "SENDER\0SENDER\0My
> > > Message \0\0" );
> > >
> >         The FileOutputStream constructor takes a filename.
> > 
> >         Anyway I don't think the win-popup message format is that simple. Ethereal
> >         probably decodes them properly. Provided you use fos.write(str) you can go
> >         back and fouth with Ethereal until the pipe mode is correct but then you'll
> >         probably need to encode the message in binary. See the
> >         jcifs/smb/SmbComXxx.java files for ideas.
> > 
> >         Mike
> 
> The messanger protocol is documented in the X/Open docs.  See:
> 
> http://www.opengroup.org/products/publications/catalog/c195.htm
> http://www.opengroup.org/products/publications/catalog/c209.htm
>