« Return to Thread: [trunk] Last API Changes for 0.3x/0.40 / close to a freeze...

Re: [trunk] Last API Changes for 0.3x/0.40 / close to a freeze...

by Bjoern Ricks-2 :: Rate this Message:

Hi

here is a short status update for all people who are waiting for the
next release ;-)

> On Sunday 29 March 2009 06:28:04 pm Daniel Gollub wrote:
> [...]
>
>> For those who don't hesitate to contribute to /trunk - please assign a
>> ticket to yourself from this query:
>> http://www.opensync.org/query?status=assigned&status=new&status=reopened&gr
>> oup=status&milestone=OpenSync+0.39
>>
>
> API breaking is nearly over. I already ported some plugins which i was able to
> build. Some plugins i hoped to since outstanding porting patches getting
> committed to SVN. Will provide new full-porting patch for those plugins which
> don't have updated yet when the other tickets got addressed.
>
> Short status updates on the API tickets:
>
>
>> Currently on our API breaking list:
>>
>> [API] OSyncObjTypeSinkFunctions struct from public API/headers
>> http://www.opensync.org/ticket/1086
>>
>
> done.
>

Yesterday we had to break this api again after spotting a big issue with
our IPC implementation. Therefore Michael Bell removed the batch_commit
callback function completely from the api. This isn't a shortcoming for
most plugins because the only plugins which used that function were
syncml and python.

>
>> -
>>
>> [API] Drop osync_objtype_set_slowsync() and add parameter osync_bool
>> *slowsync to plugin connect()
>> http://www.opensync.org/ticket/1085
>>
>
> done.
>
>
>> -
>>
>> [API] Common API interface pattern for list-implementations
>> http://www.opensync.org/ticket/975
>>
>> Björn is working on that.
>>
>
> still ongoing - expected to be complete soon.
>

Done and committed in r5448. Now all list related interface will return
a OSyncList. The returned OSyncList is always a shallow copy of an
internal opensync structure/list and has to be freed in the application
or plugin. Please be sure that osync_list_free is called on the returned
list to avoid memory leaks.

>> -
>>
>> [API] size_t/unsigned int review and cleanup
>> http://www.opensync.org/ticket/974
>>
>
> done for the public API - so not blocking anymore 0.39 milestone. Got moved to
> 0.40
>
>

Internal api still needs cleanup but it isn't blocking the next release.
This should be a trivial task too.

>> -
>>
>> Make OSyncCapabilities and the use of Merger/Demerge format independent
>> http://www.opensync.org/ticket/1084
>>
>> Still need to finish my "design" draft. As soon this is ready i'll drop a
>> new mail about this. I already started to make some notes in the wiki...
>> but it's incomplete. (This based on the previous discussion regarding
>> "native capabilities", alternative to xmlforamt and stuff like that ..)
>>
>
> This is still open ... i plan to invest today my time on that.
>
>

The discussion is still ongoing. Daniel could you write a short mail
about the current status and your planning?

>> -
>>
>> Separate static and dynamic parts of plugin/member configuration
>> http://www.opensync.org/ticket/1013
>>
>> I'm not quite sure if we still can do this without touching any API. If so
>> this is not blocking 0.39.
>>
>
> Still need to be clarified if this involves any API change. if not this is not
> blocking 0.39
>
>
>

I am not sure about this ticket and the current status. It was
originally created by Henrik. So Henrik could you write some sentences
about it?

--
/Bjoern Ricks

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel

« Return to Thread: [trunk] Last API Changes for 0.3x/0.40 / close to a freeze...