Re: [PyWrapper-devel] [tdwg-tapir] RE: WG: tapir: capabilities

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

good.=20
PyWrapper caches the metadata in a file and the provider can specify how =
often it should be updated. Usually once a day. Then its lightning fast =
except for the 1 query. But an empty metadata element is ok. The schema =
currently doesnt allow this I think. Should we make at least the =
dct:modified optional? Ah, the ABCDdiscussion again...

-- Markus
 =20

> -----Urspr=FCngliche Nachricht-----
> Von: pyw...@li...=20
> [mailto:pyw...@li...] Im=20
> Auftrag von Renato De Giovanni
> Gesendet: Montag, 31. Juli 2006 14:28
> An: tdw...@li...
> Cc: PyWrapper Developers mailing list
> Betreff: Re: [PyWrapper-devel] [tdwg-tapir] RE: WG: tapir:=20
> capabilities
>=20
> OK, Markus. Agreed.
> But maybe we could also consider an empty metadata response,=20
> because "dct:modified" will likely require interaction with=20
> the DB. And it could take some time for the larger ones=20
> (experience from DiGIR).
>=20
> Regards,
> --
> Renato
>=20
> > I have implemented the log-only request now and would like=20
> to suggest=20
> > the
> > following:
> >
> > 1) add "log-only" attribute to responeOperationGroup. Ive chosen=20
> > "log-only" cause we already have there an attribute "apply-xslt"
> > 2) add a mandatory boolean attribute "logRequestsDenied" to the=20
> > operation element in a capabilities request
> > 3) use existing responses for the log-only request. So if you do a=20
> > search with log-only active, you will get an empty search response=20
> > back. Thats much easier to implement and doesnt require any=20
> change in=20
> > the schema. The same works with inventories. Pong, Capa & Meta=20
> > responses dont cost much anyway, so we could do a normal=20
> response (if=20
> > anyway uses log-only with those requests at all)
> >
> >
> > Does everyone agree to this?
> > The schema is already updated for this.
> >
> >
> > Markus
>=20
>=20
>=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