Hi all,
According to the documentation of the history service
(http://www.sip-communicator.org/index.php/Documentation/HistoryService
) a HistoryRecordStructure can be overridden for individual records.
I wish to know if this is actually being used and if yes,then would
there be a way of doing it using the HistoryRecordStructure and
propertyValues .
Regards
Ajay
···
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
Hi Ajay,
Yes HistoryRecordStructure is currently used in two places : MessageHistoryService and CallHistoryService,
as everyone of these services is using its own structure.
What do you mean with this "would there be a way of doing it using the HistoryRecordStructure and propertyValues" ?
Currently the structure is just an array of Strings representing structure of the records, for a DB this represents the column names.
What do you think?
Cheers
damencho
AJAY CHHATWAL wrote:
···
Hi all,
According to the documentation of the history service
(http://www.sip-communicator.org/index.php/Documentation/HistoryService
) a HistoryRecordStructure can be overridden for individual records.
I wish to know if this is actually being used and if yes,then would
there be a way of doing it using the HistoryRecordStructure and
propertyValues .
Regards
Ajay
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
Hi damencho
Thanks for your quick response...Actually I wish to know if the
HistoryRecordStructure is overridden for individual records anywhere
or is a common HistoryRecordStructure used throughout the
history....And if yes,is there a way to achieve the same functionality
without overriding the HistoryRecordStructure for individual records
Regards
Ajay
···
On Thu, May 28, 2009 at 1:12 PM, Damian Minkov <damencho@sip-communicator.org> wrote:
Hi Ajay,
Yes HistoryRecordStructure is currently used in two places :
MessageHistoryService and CallHistoryService,
as everyone of these services is using its own structure.
What do you mean with this "would there be a way of doing it using the
HistoryRecordStructure and propertyValues" ?
Currently the structure is just an array of Strings representing structure
of the records, for a DB this represents the column names.
What do you think?
Cheers
damencho
AJAY CHHATWAL wrote:
Hi all,
According to the documentation of the history service
(http://www.sip-communicator.org/index.php/Documentation/HistoryService
) a HistoryRecordStructure can be overridden for individual records.
I wish to know if this is actually being used and if yes,then would
there be a way of doing it using the HistoryRecordStructure and
propertyValues .
Regards
Ajay
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
Hi,
the structure is not overridden its used as its.
How do you think to achieve this ? Have you came up already with some scheme of the database ?
damencho
AJAY CHHATWAL wrote:
···
Hi damencho
Thanks for your quick response...Actually I wish to know if the
HistoryRecordStructure is overridden for individual records anywhere
or is a common HistoryRecordStructure used throughout the
history....And if yes,is there a way to achieve the same functionality
without overriding the HistoryRecordStructure for individual records
Regards
Ajay
On Thu, May 28, 2009 at 1:12 PM, Damian Minkov > <damencho@sip-communicator.org> wrote:
Hi Ajay,
Yes HistoryRecordStructure is currently used in two places :
MessageHistoryService and CallHistoryService,
as everyone of these services is using its own structure.
What do you mean with this "would there be a way of doing it using the
HistoryRecordStructure and propertyValues" ?
Currently the structure is just an array of Strings representing structure
of the records, for a DB this represents the column names.
What do you think?
Cheers
damencho
AJAY CHHATWAL wrote:
Hi all,
According to the documentation of the history service
(http://www.sip-communicator.org/index.php/Documentation/HistoryService
) a HistoryRecordStructure can be overridden for individual records.
I wish to know if this is actually being used and if yes,then would
there be a way of doing it using the HistoryRecordStructure and
propertyValues .
Regards
Ajay
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
Hi emil,damencho,
Thanks for your response.
I am currently implementing the HistoryService using the new
DatabaseService developed by me.
I intend to represent each history as a table in the database.The
propertyNames in the HistoryRecordStructure naturally correspond to
the column names in the table.
If the number of columns is fixed i.e. there is no overridding in
individual records,then I can simply create the table with the columns
corresponding to the HistoryRecordStructure of the corresponding
history.Otherwise,since it is not possible to have variable no. of
columns in the DB,I shall have to do it some other way which would
impact the performance of searching etc.
I have also talked to my mentor (Benoit Pradelle) about this feature
(overriding) and he asked me to enforce a more constrained way of
working prohibiting this if no other bundle was dependent on it.
Regards
Ajay
···
On Thu, May 28, 2009 at 4:34 PM, Damian Minkov <damencho@sip-communicator.org> wrote:
Hi,
the structure is not overridden its used as its.
How do you think to achieve this ? Have you came up already with some scheme
of the database ?
damencho
AJAY CHHATWAL wrote:
Hi damencho
Thanks for your quick response...Actually I wish to know if the
HistoryRecordStructure is overridden for individual records anywhere
or is a common HistoryRecordStructure used throughout the
history....And if yes,is there a way to achieve the same functionality
without overriding the HistoryRecordStructure for individual records
Regards
Ajay
On Thu, May 28, 2009 at 1:12 PM, Damian Minkov >> <damencho@sip-communicator.org> wrote:
Hi Ajay,
Yes HistoryRecordStructure is currently used in two places :
MessageHistoryService and CallHistoryService,
as everyone of these services is using its own structure.
What do you mean with this "would there be a way of doing it using the
HistoryRecordStructure and propertyValues" ?
Currently the structure is just an array of Strings representing
structure
of the records, for a DB this represents the column names.
What do you think?
Cheers
damencho
AJAY CHHATWAL wrote:
Hi all,
According to the documentation of the history service
(http://www.sip-communicator.org/index.php/Documentation/HistoryService
) a HistoryRecordStructure can be overridden for individual records.
I wish to know if this is actually being used and if yes,then would
there be a way of doing it using the HistoryRecordStructure and
propertyValues .
Regards
Ajay
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
Hi again,
the propertyNames in the HistoryRecordStructure must be a constant, but recently(last year) we had to change
the MessageHistory service and we add one more field. This was the only situation I was thinking of.
But of course we can stick for now to the situation where this fields are constant and at later stage we can do some kind of one time checking the structure of the tables and if needed we can add some columns or something similar.
damencho
AJAY CHHATWAL wrote:
···
Hi emil,damencho,
Thanks for your response.
I am currently implementing the HistoryService using the new
DatabaseService developed by me.
I intend to represent each history as a table in the database.The
propertyNames in the HistoryRecordStructure naturally correspond to
the column names in the table.
If the number of columns is fixed i.e. there is no overridding in
individual records,then I can simply create the table with the columns
corresponding to the HistoryRecordStructure of the corresponding
history.Otherwise,since it is not possible to have variable no. of
columns in the DB,I shall have to do it some other way which would
impact the performance of searching etc.
I have also talked to my mentor (Benoit Pradelle) about this feature
(overriding) and he asked me to enforce a more constrained way of
working prohibiting this if no other bundle was dependent on it.
Regards
Ajay
On Thu, May 28, 2009 at 4:34 PM, Damian Minkov > <damencho@sip-communicator.org> wrote:
Hi,
the structure is not overridden its used as its.
How do you think to achieve this ? Have you came up already with some scheme
of the database ?
damencho
AJAY CHHATWAL wrote:
Hi damencho
Thanks for your quick response...Actually I wish to know if the
HistoryRecordStructure is overridden for individual records anywhere
or is a common HistoryRecordStructure used throughout the
history....And if yes,is there a way to achieve the same functionality
without overriding the HistoryRecordStructure for individual records
Regards
Ajay
On Thu, May 28, 2009 at 1:12 PM, Damian Minkov >>> <damencho@sip-communicator.org> wrote:
Hi Ajay,
Yes HistoryRecordStructure is currently used in two places :
MessageHistoryService and CallHistoryService,
as everyone of these services is using its own structure.
What do you mean with this "would there be a way of doing it using the
HistoryRecordStructure and propertyValues" ?
Currently the structure is just an array of Strings representing
structure
of the records, for a DB this represents the column names.
What do you think?
Cheers
damencho
AJAY CHHATWAL wrote:
Hi all,
According to the documentation of the history service
(http://www.sip-communicator.org/index.php/Documentation/HistoryService
) a HistoryRecordStructure can be overridden for individual records.
I wish to know if this is actually being used and if yes,then would
there be a way of doing it using the HistoryRecordStructure and
propertyValues .
Regards
Ajay
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
Hi demencho,
Well then I'll be implementing the History Service assuming that the
fields are constant i.e. Individual records can not override the
HistoryRecordStructure
Regards
Ajay
···
On Thu, May 28, 2009 at 8:41 PM, Damian Minkov <damencho@sip-communicator.org> wrote:
Hi again,
the propertyNames in the HistoryRecordStructure must be a constant, but
recently(last year) we had to change
the MessageHistory service and we add one more field. This was the only
situation I was thinking of.
But of course we can stick for now to the situation where this fields are
constant and at later stage we can do some kind of one time checking the
structure of the tables and if needed we can add some columns or something
similar.
damencho
AJAY CHHATWAL wrote:
Hi emil,damencho,
Thanks for your response.
I am currently implementing the HistoryService using the new
DatabaseService developed by me.
I intend to represent each history as a table in the database.The
propertyNames in the HistoryRecordStructure naturally correspond to
the column names in the table.
If the number of columns is fixed i.e. there is no overridding in
individual records,then I can simply create the table with the columns
corresponding to the HistoryRecordStructure of the corresponding
history.Otherwise,since it is not possible to have variable no. of
columns in the DB,I shall have to do it some other way which would
impact the performance of searching etc.
I have also talked to my mentor (Benoit Pradelle) about this feature
(overriding) and he asked me to enforce a more constrained way of
working prohibiting this if no other bundle was dependent on it.
Regards
Ajay
On Thu, May 28, 2009 at 4:34 PM, Damian Minkov >> <damencho@sip-communicator.org> wrote:
Hi,
the structure is not overridden its used as its.
How do you think to achieve this ? Have you came up already with some
scheme
of the database ?
damencho
AJAY CHHATWAL wrote:
Hi damencho
Thanks for your quick response...Actually I wish to know if the
HistoryRecordStructure is overridden for individual records anywhere
or is a common HistoryRecordStructure used throughout the
history....And if yes,is there a way to achieve the same functionality
without overriding the HistoryRecordStructure for individual records
Regards
Ajay
On Thu, May 28, 2009 at 1:12 PM, Damian Minkov >>>> <damencho@sip-communicator.org> wrote:
Hi Ajay,
Yes HistoryRecordStructure is currently used in two places :
MessageHistoryService and CallHistoryService,
as everyone of these services is using its own structure.
What do you mean with this "would there be a way of doing it using the
HistoryRecordStructure and propertyValues" ?
Currently the structure is just an array of Strings representing
structure
of the records, for a DB this represents the column names.
What do you think?
Cheers
damencho
AJAY CHHATWAL wrote:
Hi all,
According to the documentation of the history service
(http://www.sip-communicator.org/index.php/Documentation/HistoryService
) a HistoryRecordStructure can be overridden for individual records.
I wish to know if this is actually being used and if yes,then would
there be a way of doing it using the HistoryRecordStructure and
propertyValues .
Regards
Ajay
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail:
dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net