On Nov 26, 2009, at 2:05 AM, Thomas Bellman wrote:
> Luke Kanies wrote:
>
>> The problem with the facts, and I believe this is
>> unique to the fact/catalog coupling, is that the compiling server
>> needs access to the client's facts, and we'd prefer to do that over
>> two queries rather than one.
>
> Is two queries really better than one? Remembering the facts for
> a client for an indeterminate time sounds to me like it would make
> puppetmasterd more complicated.
>
> From what I can remember and understood from the earlier discussion,
> the only reason for having two queries would be to work around a
> limitation when using GET with some webservers, and the reason we
> use GET is because the REST paradigm tells us do that. But does
> that rule really give us some advantage, or is it just an ivory
> tower proclamation that you are unclean if you don't?
In our case it's not so much that we have an ivory tower but that we
have a system implemented around GET, with no real provision for ever
using POST. Not that it's impossible, but it'd be a one-off for both
client and server, or it would drastically complicate the model we use
for passing information around the network.
Hmm, well, maybe not drastically; I suppose we could have an argument
that causes the equivalent of a 'get' to be returned as the result of
the original call. That's still a significant change -- would we have
to change our 'put' to a 'post'? -- but not untenable, I think.
--
The great aim of education is not knowledge but action.
-- Herbert Spencer
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
