Re: DSML.pm and DSML pretty print option request.

[Clif H. <cl...@di...>]

> 
> On Mon, Jul 29, 2002 at 09:24:21AM -0500, Clif Harden wrote:
> > 
> > Graham,
> > 
> > I found another problem with the dsml module.
> > It is not base64 encoding binary attributes.
> 
> Can you send a testcase.


I will send you one.




> 
> Soon I should have the cpan RT system sending/monitoring
> the mailing list so that bugs would then be sent to
> bug...@rt...
> 
> > Also do we still need the DSML directory since 
> > we are no longer using XML::Parser.
> 
> No we don't. The tarball should not create it. If you have one
> it will be a leftover from a previous install.


It will be gone soon.


> 
> > Now for the pretty print option request.
> > 
> > Currently when we do a pretty print we use 1 as the
> > option value.  This will insert a "\n" between elements
> > so that it can be read easily on a UNIX system.
> > 
> > It would be nice to have an option value of 2 so that
> > we could insert a "\r\n" between elements so that 
> > the data could be easily read on a PC.  I have a soap
> > server and Visual Basic system that could use the
> > option.  
> 
> You mean you are creating the file on a UNIX box, and transfering
> to a PC ?

NO! I am not that dumb! 

I do a LDAP request to my SOAP server, the server does the Net::LDAP 
work, and sends back the LDAP data as XML.  It is all message traffic 
and gets around all of the problems assoicated with M$ ADO.  Unix 
systems can use it too.  Pretty slick system, but still needs some 
work to make it really usefull.

It is a very simple SOAP client/server system.  

> 
> Rather than adding a option 2, I would preer the user to specify
> the line ending characters. Maybe we change the pretty option
> to pass the line ending characters wanted, or we add another
> option to do that.

Specifing the line ending characters is probably the best solution.
Then it is up to the programmer to decide what to use and it makes
it platform independent.


> 
> Graham.
> 
> 


Clif