Skip to Content.
Sympa Menu

perfsonar-dev - Re: required properties for xml db

Subject: perfsonar development work

List archive

Re: required properties for xml db


Chronological Thread 
  • From: Maciej Glowiak <>
  • To: Loukik Kudarimoti <>
  • Cc: Roman Lapcz <>,
  • Subject: Re: required properties for xml db
  • Date: Wed, 09 Aug 2006 13:24:22 +0200
  • Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA CXBIWXMAAEU1AABFNQF8gVf5AAAAB3RJTUUH1QYQDjo6uEWvwgAAAM5JREFUGNNN0LFqAkEUheGj KRZsfATrvENgYyH4APabxwgWGUUQC99BsNDCInUq7VImbbDZ0kayxBXMuN7jvTuKVh//mZlmQKZ1 EhQ8GAVgZECspEBdWQHRjR70KlgFKkoUaCw3ijSYQ4n5HfBK4a4jDcdDQPol/80Sr9BxZOOL4Fmr Jq8VBx7eopaSPvWGOm67fqol3j1q0XNs7Nk2cs6MU6gPNzf+ZGKQX4Ek8H6rAnFZnXB2vJxJcv8g C2P+WzL4tD+Txc4KydrIkh+eAdo01QbjQ84vAAAAAElFTkSuQmCC
  • Organization: Poznan Supercomputing and Networking Center

Loukik,

Just some additional thoughts.

Loukik Kudarimoti napisaƂ(a):
Hi Roman and Maciej,

From SQL MA, I found out that the following properties are being used in order to determine the type of access to xmldb and also the access related parameters.

component.ma.xmldb.db_uri
component.ma.xmldb.db_username
component.ma.xmldb.db_password
component.ma.xmldb.db_status
component.ma.xmldb.db_access
component.ma.xmldb.db_uri.xmlrpc

Can you please help me in understanding the purpose and the way to use the following properties

component.ma.xmldb.db_uri.xmlrpc and component.ma.xmldb.db_uri
-> do we need both of them?

component.ma.xmldb.db_status
-> what does this mean? If its off, does the storage manager automatically read from an xml file instead?

I would like to make use of the existDb but I see that I need to pass the names of these properties. I suggest we fix the name of these properties and read them directly in the factory so that
* Each service doesn't need to pass them. Invocation becomes simpler.

First I created Storage Manager in Components architecture because of performance. But as I tested later, the performance was exactly the same, so using component is unnecessary complication.

The simplest way of using Storage Manager is the way I followed in the LS. (XmlLsTypeServiceEngine.java).

I left old functionality to avoid crash of other services that used this Storage Manager. But I think we should migrate towards using Storage Manager directly

* We have the same property names for all the services. That way we avoid duplicate entries and its easier to manage and understand.

I agree, that properties names should be unified, but it may be not so simple, especially if you need to use different Storage Managers (probably there would be a need for using it in LS when we had AA)

But,as I told you by phone: I agree it could be done better. I'll talk to Roman about it and we'll find a consensus :)

Maciej


--

--------------------------------------------------------------------
| Maciej Glowiak Network Research and Development ||
|

Poznan Supercomputing and Networking Center ||
| (+48 61) 858 2024 http://monstera.man.poznan.pl/ ||
====================================================================



Archive powered by MHonArc 2.6.16.

Top of Page