ComponentConfig

#1

Hi Tobias.

As an idea to improve API:

It could be common to have several instances of the same components in several native workers with different extra configurations.

It will be nice to have access to worker id and component id from a component instance.

For definition of register/publish urls as a example.

Otherwise it is necessary to repeat this info in extra configurations. That can lead to errors.

Thanks,

Serge

0 Likes

#2

The worker ID or component ID an app component is running under must be of no concern to the app component itself. These are Crossbar.io deployment details and hidden from app code by design.

Rgd your actual itch of starting many components with varied configs: automation of such things will be avail soon via a Crossbar.io management API (which itself is WAMP based).

Currently, only node local static config is there, but the mgmt API will allow dynamic and scripted configutation - without node restarts.

···

Sent from Mobile (Google Nexus 5)

Am 03.04.2015 9:20 nachm. schrieb “Serge Voloshenyuk” volos...@gmail.com:

Hi Tobias.

As an idea to improve API:

It could be common to have several instances of the same components in several native workers with different extra configurations.

It will be nice to have access to worker id and component id from a component instance.

For definition of register/publish urls as a example.

Otherwise it is necessary to repeat this info in extra configurations. That can lead to errors.

Thanks,

Serge

You received this message because you are subscribed to the Google Groups “Crossbar” group.

To unsubscribe from this group and stop receiving emails from it, send an email to crossbario+...@googlegroups.com.

To post to this group, send email to cross...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/crossbario/f93edb8f-5654-4c6c-8dac-2ca805eb0be7%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

0 Likes

#3

Rgd your actual itch of starting many components with varied configs: automation of such things will be avail soon via a Crossbar.io management API (which itself is WAMP based).

It’s interesting for me.

Additional info for your API design:

There are not only different instances of the same component

but different components used standard services needed unique identification.

For example:

logging handler that emit log records through WAMP topics.

it will be easy if this handler could configure itself through worker/component context.

···

пятница, 10 апреля 2015 г., 19:02:45 UTC+3 пользователь Tobias Oberstein написал:

0 Likes