For traditional blog posting yes, such a tight coupling between linked
content and the entry content would be surprising. For the use cases
we're tackling and for the type of application we're building, it's not.
Regardless, the tight binding between the post and the linked resources
is somewhat secondary to the issue of having to coordinate multiple post
and put operations just to perform a single blog post. If I want to
post an entry that links to five different images, I shouldn't have to
do six different POST operations.
In any case, as Rob indicated, all we want to know right now is whether
others are seeing this problem and whether or not anyone thinks there
might be an interop problem lurking around in here somewhere.
- James
Joe Gregorio wrote:
On 2/7/06, rob yates <[EMAIL PROTECTED]> wrote:
Joe,
You lost me there. Are you saying that if I create a weblog
entry that includes a picture and later delete that entry you
want the associated pciture to be deleted also?
yes
May I presume this is a requirement based on your server
implementation, because there is no requiement for such
behavior in the APP spec.
it is a requirement for our implementations yes, we are wondering
whether other's are seeing this requirement in their implementations.
i.e. the need to manage the lifecycle and access control for embedded
media with its associated entry.
For my implementations I do not see this requirement. If I post
a picture I may use it in multiple entries or even use it under a
different CMS on a wholly different machine. I would find
such a tight binding between the lifetime of a picture and the
first entry that it was used in quite suprising.
-joe
--
Joe Gregorio http://bitworking.org
