Re: [Ekiga-devel-list] Code in lib/engine/components/opal/

[Julien Puydt <jpuydt free fr>]

Le 28/01/2013 18:12, Eugen Dedu a écrit :
> I cannot say anything on all this, except: can we use more meaningful
> words than bank and dialect? Is bank a registrar? For me, bank is for
> money. What is a dialect (a version of a spoken language?)?

A bank is where accounts are kept.

A dialect is a way to send/receive message.

I found Ekiga::Bank would be better than Ekiga::AccountLister, and 
Ekiga::Dialect better than Ekiga::SomeWayToSendAMessage.


> You propose PresentityDecorator and ContactDecorator? What do these
> words mean? Decorator is for GUI things, is that the case?

No, decorator is the name of a well-known design pattern ; it's a way to 
add features to objects : it can be used for gui, but it's more general.

Those abstract classes are something which is already in ekiga ; it's 
just that instead of making the Opal::Sip::EndPoint an implementation of 
those classes, I propose to make Opal::Bank an implementation of those 
classes.

> I would also like to change roster (who in this list knows what it
> means?) to local contacts or something like this. No software I know
> uses the word "roster".

Well :

1) roster is a correct english word to describe a list of 
people/contacts : http://en.wikipedia.org/wiki/Roster

2) roster is the name of a contact list in the jabber protocol, see 
http://xmpp.org/rfcs/rfc6121.html

3) a roster doesn't have to be local ; in fact we have a local-roster 
which is used for the opal part of ekiga, but the loudmouth plugin 
provides rosters which are kept on-server.

Snark