Luke Kanies wrote:
> Again, that doesn't solve the real problem - I want a Facts post to
> return a Catalog. How, as the client, would I tell the server that?
>
> Or do we just always return a catalog when someone posts facts? That
> seems a bit overkill.
I get the impression that you need to take a step back and look at things
from a slightly higher level. Is uploading facts really an operation
that we want a client to do? If so, for what reason? Isn't the operation
we want really "get catalog based on the following facts"? Then we will
simply say that a client SHOULD do that by doing
POST /myenvironment/catalog HTTP/1.0
<facts>...
but MAY do it using
GET /myenvironment/catalog?<facts>... HTTP/1.0
(I don't remember the exact syntax for posting a form in HTTP off hand.)
In the server both would be handled identically after decoding the
GET/POST and the "form data". I haven't looked at that code in Puppet,
but any reasonable framework for handling HTTP requests should make it
pretty easy to handle them identically.
/Bellman
--
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.
