• Your recent searches
AFS-Command
20 results

 view release on metacpan or  search on metacpan

ToDo.html  view on Meta::CPAN 

    <HTML> 
	<HEAD> 
	    <TITLE>distro/ToDo</TITLE> 
	</HEAD>

	<BODY>

<!-- INDEX BEGIN -->

<UL>

	<LI><A HREF="#NAME">NAME</A>
	<LI><A HREF="#Enhancements">Enhancements</A>
	<UL>

		<LI><A HREF="#Accept_AFS_Object_objects_as_ar">Accept AFS::Object objects as arguments</A>
		<LI><A HREF="#stderr_handling">stderr handling</A>
		<LI><A HREF="#Test_Suite_fs_lsmount_using_mul">Test Suite: fs lsmount using multiple dirs</A>
	</UL>

	<LI><A HREF="#Bugs">Bugs</A>
	<UL>

		<LI><A HREF="#stdout_stderr_buffering_will_bre">stdout/stderr buffering will break the fs examine/diskfree commands</A>
	</UL>

</UL>
<!-- INDEX END -->

<HR>
<P>
<H1><A NAME="NAME">NAME

</A></H1>
AFS::Command ToDo List


<P>

<P>
<HR>
<H1><A NAME="Enhancements">Enhancements

</A></H1>
<P>
<HR>
<H2><A NAME="Accept_AFS_Object_objects_as_ar">Accept AFS::Object objects as arguments

</A></H2>
Methods like $fs-&gt;listacl() return these handy little AFS::Object::ACL
objects. It would be nice if we could manipulate them via OO method calls,
and then pass them right back to $fs-&gt;setacl(), wouldn't it?


<P>

And how about passing the AFS::Object::Path objects returned from
$fs-&gt;whichcell directly to an $fs-&gt;listquota call, so that the final
AFS::Object::Path objects have all of the attributes returned by both
calls, but in one set of objects?


<P>

Look for this in version 1.1


<P>

<P>
<HR>
<H2><A NAME="stderr_handling">stderr handling

</A></H2>
stderr processing needs to be handled in the <CODE>_exec_cmds()</CODE>
method, and for that matter, <CODE>_reap_cmds()</CODE> needs to be folded
into <CODE>_exec_cmds().</CODE>


<P>

The problem is that each API method calls <CODE>_save_stderr(),</CODE> and
then later calls <CODE>_restore_stderr(),</CODE> and we leave stderr
redirected for longer than necessary. The contents of the redirected output
should be *only* the output from the commands we run, and right now, some
of our own carping can creep in there.


<P>

Worse, its possible that a failure in the API can leave stderr redirected,
resulting in a lot of confusion.


<P>

Its possible we should just suck in *ALL* of the output, both
stdout/stderr, and drop that data into a couple of arrays. Then, method
calls on the command object get gets individual rows of stdout/stderr
output.


<P>

<PRE>  return unless $self-&gt;_exec_cmds();
</PRE>

<P>

<PRE>  #
  # Process stdout
  #
  while ( defined($_ = $self-&gt;_stdout() ) ) {
</PRE>

<P>

<PRE>  }
</PRE>



( run in 0.973 second using v1.01-cache-2.11-cpan-cdf2f3d4e48 )