alfs: next aspect to code?
mr.subhash at gmail.com
Sun Nov 27 03:27:38 PST 2005
i would suggest to go for authentication.
That doesn't need discussion about the design aspect and would be a
trouble later on when the project grows bigger.
On 11/27/05, Thomas Pegg <thomasp at linuxfromscratch.org> wrote:
> Jeremy Huntwork wrote:
> > Hey Guys,
> > alfs connects to alfsd and then prompts for input. (Try entering a
> > command with some extended output, like 'ps aux' :) )
> Works pretty nicely except that the output gets cut off after a bit, may
> be something to look into.
> > So my question is, what's next? What should be the next aspect we try to
> > incorporate?
> Not really a code aspect, but more of a design aspect, maybe the next
> would be to decide what kind of information and how is that information
> going to be transferred between the client and server. I think this
> should be concentrated on for now so we can figure out how to handle the
> various interactions between client and server, such as handling the
> older xml profiles, profiles in a potentially new format,
> authentication, etc.
> FAQ: http://www.linuxfromscratch.org/faq/
> Unsubscribe: See the above information page
║I don't know how much of what I say is true ║
More information about the alfs-discuss