[C++ native] Porting to embedded platform

[Shivakumar Balasubramanyam <sh...@gmail.com>]

Folks,

I would like to get some feedback from C++ developers from both server and
embedded platforms.

After reviewing the code, I would like to get some feedback in reducing the
footprint of the code and also some help in adding extensions to unsupported
transport/transport protocol.

Some things I would like to know are,

1. Abstracting SDO from XML dependency.

2. The extensions avaialble do not have a consistent form, which is the most
appropriate model to follow? (cpp, ws, rest?)

3. Customization of the serialization libary? How is this configured?

I would also like to know what changes are done in the trunk now from the
last released version of SCA Native?

Thanks,
Shiva

RE: [C++ native] Porting to embedded platform

["Balasubramanyam, Shivakumar" <sb...@qualcomm.com>]

Hi Simon,
 
2. The extensions avaialble do not have a consistent form, which is the
most
appropriate model to follow? (cpp, ws, rest?)

I'm not sure but the cpp and ws have been around the longest. In what
way do you see that they are inconsistent? 
 
[Shiva]  Mostly in the way the code is arranged for extending the
services.  I am still trying to understand how the code is arranged to
add an extension.
 
For example, [Correct me if I am wrong]
 
runtime/extensions/cpp/src/osoa 
    Contains code for CPP runtime.
 
runtime/extensions/cpp/src/tuscany
    Contains runtime support for shared object implementations [local
services].     Has code under tuscany/sca/cpp/ and tuscany/sca/cpp/model
 
runtime/extensions/ws
    Contains reference and service
 
runtime/extensions/rest
    Contains interface, reference and service
 
What would be the process in adding an cpp extension that would support
a shared_memory transport with a binary serialization protocol. lets say
TLV format for the sake of discussion.
 
Where would the implementation reside? runtime/extensions/shared_memory?

 
3. Customization of the serialization libary? How is this configured?

Do you mean libxml used by SDO? 
 
Yes. I would to see if I can pluging DAS for Binary protocol or some
custom requirement. 
 

Re: [C++ native] Porting to embedded platform

[Simon Laws <si...@googlemail.com>]

Hi Shiva

I noticed you didn't get any response. It's a while since I worked on SCA
native but I'll give you my opinion. See comments in line.

Regards

Simon

On Wed, Jun 25, 2008 at 12:20 AM, Shivakumar Balasubramanyam <
shivsbala@gmail.com> wrote:

> Folks,
>
> I would like to get some feedback from C++ developers from both server and
> embedded platforms.
>
> After reviewing the code, I would like to get some feedback in reducing the
> footprint of the code and also some help in adding extensions to
> unsupported
> transport/transport protocol.
>
> Some things I would like to know are,
>
> 1. Abstracting SDO from XML dependency.


I think this would be a good idea. I guess a databinding framework is
required like we have in the java implementation.


>
>
> 2. The extensions avaialble do not have a consistent form, which is the
> most
> appropriate model to follow? (cpp, ws, rest?)


I'm not sure but the cpp and ws have been around the longest. In what way do
you see that they are inconsistent?


>
>
> 3. Customization of the serialization libary? How is this configured?


Do you mean libxml used by SDO?


>
>
> I would also like to know what changes are done in the trunk now from the
> last released version of SCA Native?


I think the main changes were sorting out the build system. Looking back the
tag for M3 was at revison 524039 in subversion so you could take a look at
the commits since then to get a feel for what has changed.


>
>
> Thanks,
> Shiva
>