Re: [PyWrapper-devel] tapir get requests & views

[<m.d...@BG...>]

Hello,
turning off the envelope meant for me only to return the pure content - =
for example an ABCD record. It was mainly inspired to have a "view" on a =
single ID to get only the XML describing the object. Or to get pure RSS =
or KML for several objects.=20

If its only to turn off the header and diagnostics I think we wouldnt =
need it, a client would have to deal with TAPIR anyway.


-- Markus
 =20

> -----Urspr=FCngliche Nachricht-----
> Von: pyw...@li...=20
> [mailto:pyw...@li...] Im=20
> Auftrag von Renato De Giovanni
> Gesendet: Mittwoch, 19. Juli 2006 21:53
> An: pyw...@li...
> Betreff: Re: [PyWrapper-devel] tapir get requests & views
>=20
> Hi,
>=20
> > Im checking the GET invoked operations now and I cant remember the=20
> > reason why we introduced another view request. We should provide=20
> > Charles some arguments why it exists and why we didnt just include=20
> > template as a parameter in inventories and searches. What was wrong=20
> > about that?
>=20
> As I said, the only reason for the view operation was to=20
> accommodate TAPIRLite providers. Apparently it was the=20
> easiest way to do that.=20
> Remeber their requirements:
>=20
> * No need to parse XML requests (only GET requests with=20
> simple key/value parameters)
> * No need to parse filters.
> * No need to implement "partial".
> * All queries based on templates.
>=20
> There could be other ways to allow the existence of TAPIRLite=20
> without having the view operation, such as including many new=20
> attributes in the search operation capabilities, but it would=20
> easily get confusing and contradictory, I think.
>=20
> Searches and inventories can make use of templates already,=20
> can't they? (at least in XML requests, but I don't see why=20
> not via GET requests as well).
>=20
> > - is the envelope turned off or on when non view requests=20
> are called=20
> > via GET? I thought its turned off then. Am I right?
>=20
> If this is not documented/defined somewhere I would suggest=20
> to turn on the envelope by default for all non view requests.
>=20
> > - inventories without envelope need some embracing root=20
> element above=20
> > the <record> elements. So should we answer with <tapir:inventory> ?
>=20
> I understood that turning off envelopes just meant removing=20
> header and diagnostics. The root element would still be <response>.
>=20
> > - If so, shouldnt we do the same for the other operations (with=20
> > exception of views maybe - well, actually an inventory view has the=20
> > same problem!). If we would do so, the summary element for=20
> paging is=20
> > there as well and we would not need to turn on the entire=20
> envelope for=20
> > counts.
> > - if not, what about ping?
>=20
> Same answer above.
> =20
> > Looks like I am discovering ever more little questions.
> > Stay tuned.
>=20
> No worries, let's kill them all!
> --
> Renato
>=20
> --------------------------------------------------------------
> -----------
> Take Surveys. Earn Cash. Influence the Future of IT Join=20
> SourceForge.net's Techsay panel and you'll get the chance to=20
> share your opinions on IT & business topics through brief=20
> surveys -- and earn cash=20
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge
&CID=3DDEVDEV
> _______________________________________________
> PyWrapper-devel mailing list
> PyW...@li...
> https://lists.sourceforge.net/lists/listinfo/pywrapper-devel
>=20