SC Profile Manager dev blog

Activity log – Week #1

Posted in Profile Manager System by scprofile on May 31, 2008


The week I’ve done some light research on the ConfigurationService and the FileAccessService and I’ve found that two files are called by other services (JmfDeviceDetector and the MetaContactListService) and the access to the main config file (sip-communicator.xml) is written directly in the method : ConfigurationServiceImpl.createConfigurationFile().

I also work on the profile manager storage system.
A profile is defined by :

  • an ID
  • a name : for example Damien or Emil
  • a path : where the data of the profile will be stored.
    This path might be enter by the user or generated automatically using this scheme :

    • XXXXX : is the date in hexadecimal in uppercase
    • name : is the name of the profile in lowercase

Here is an example of the future profile.xml file.

    <lastProfile value="1" />
    <useDefault value="true" />
        <profile id="1">
            <name value="default" />
            <path value="/home/damien/.sip-communicator/SC.A12F3.default" />
        <profile id="2">
            <name value="Damien" />
            <path value="/home/damien/SC/profile" />

The first value store the last profile used
The second one define if we need to ask for a profile or use the default one (ie the last profile used)
Then the list of the profiles. A field which store the next id might be add.

Today I will begin the implementation of the new Service and more specifically on the methods to read this file and  keep it updated.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: