Hi:
> -----Original Message-----
> From: Dev [mailto:[email protected]] On Behalf Of Dominig ar Foll
> Sent: Monday, December 08, 2014 4:28
> To: [email protected]
> Subject: Re: [Dev] FW: bluetooth-frwk changes
>
> Hello,
>
> I am afraid that I would rather see the code been cleaned up than to be
> sliced in small thunk to keep non functional code that might be used
> somewhere else.
>
> The source management model that we use in Tizen, allows us to progress
> Tizen 3 without affecting Tizen 2 legacy and we shall take profit of that
> feature.
>
> In short we need to keep the common part runing on Common code and let the
> profile define patches if they have very specific use case, what I hope will
> be the exception.
The idea, and concept is quite right, we should not let different profiles
affect each other, and tizen-3.0 affect the legacy.
And the profile define patches also can help, but maintain patches to different
profile is not easy. We also need to think of this from the architecture level.
And let architecture suitable for different profile is required. We should
abstract the common operation/functionality, and define the platform/profile
layer(plugin) to different profile and usage. So to different platform/profile
should load different plugin. We can see this kind of design at many projects
like Kernel, oFono and so on. But the current Bluetooth framework does has this
concept. That is the reason why we have platform/profile plugin in NTB.
Thanks!
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
