Re: How a CLI could use the client environment executables files?

Thanks Mike,

you are right, I have to make decisions in what concerns the
architecture of my client but that is not REST related. But I don't
know at which level it is important or not that the consumer of the
user agent knows about those details.

On Fri, Jun 1, 2012 at 10:14 PM, mike amundsen <[email protected]> wrote:
> Philippe:
>
> sounds like an interesting project.
>
> first, the REST style focuses primarily on the network-level software
> details; the implementation within the servers and clients is left open for
> your own choices.
>
> However, Chapter 1 of Fielding's dissertation does a good job of describing
> the primary software model he had in mind esp. section 1.2[1]. I think
> you'll find some guidance there and see that your idea of using internal
> components on the client (i.e. diff, etc.) is well within the scope of an
> implementation w/ REST characteristics.
>
> Hope this helps.
>
> [1] http://www.ics.uci.edu/~fielding/pubs/dissertation/software_arch.htm#sec_1_2
>
> mca
> http://amundsen.com/blog/
> http://twitter.com@mamund
> http://mamund.com/foaf.rdf#me
>
>
>
>
> On Fri, Jun 1, 2012 at 7:12 PM, Philippe Rathé <[email protected]> wrote:
>>
>> Hello all,
>>
>> I would like to code my own atompub client and server. I use atompub
>> to expose different hierarchical collections of members.I would like
>> the client being an interactive command line tool. Additionally to be
>> used as a feed reader, a consumer of the CLI would probably use it
>> for: bookmarking a collection; refreshing bookmarked collections;
>> using diff tools to compare local files and then POSTing the output
>> content to a collection; etc.
>>
>> The biggest challenge I face is how the CLI could use the client
>> environment executables files restfully?
>>
>> I need to access the diff tools on the client-side system. Does it
>> fail any constraints the fact that the CLI would try to access the
>> diff executable tools under the hood? I would provide to the consumer
>> the hypermedia controls necessary to fill in the arguments that will
>> be passed to the executables. Just like HTML forms. What about
>> code-on-demand instead? The client would executes, as an example,
>> shell scripting fragment depending on the client environment setup
>> capabilities. Just like the browser executes JavaScript? It has some
>> advantages that the client could be partly able to update itself.
>>
>> Otherwise I would need to let the server do the diff which will be
>> retrieve by the client. But the client and the server will most of the
>> time be on the same machine or local network. The client needs to
>> access the file system and do operations on files, which the local web
>> server could do.
>>
>> Any advices? Thanks.
>> -- Philippe
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>