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

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

by Daniel Gollub-2 :: Rate this Message:

Reply to Author | View in Thread

Hi,

Björn and I do currently the last API cleanups. The python wrapper is
currently not building due to all this changes. The wrapper doesn't have high
priority as stabilizing the (C) API. (It's up for takers if someone wants to
port the wrapper ... otherwise i'll do that right before tagging 0.39).

Since this are lots of API changes - i try to make this quick and painless for
you. So please standby till Monday. I hope to to get everything inside SVN
this night. Only #1013 and #1084 might take more time.

Why we do all those changes now?
Because we hope to not break the API in near future at all... and make things
stable for plugin/application development.

As soon as listed things are done i'll provide patches for all plugins I'm
able to build. If you want to port your plugin on your own - and have any
questions or problems. Don't waste time and feel free to contact me
immediately - or try to catch Björn on IRC ;)

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&group=status&milestone=OpenSync+0.39


Currently on our API breaking list:

[API] OSyncObjTypeSinkFunctions struct from public API/headers
http://www.opensync.org/ticket/1086

This struct is the last public struct in the API. For API maintenance reason i
would like to remove this to make the API more stable. This requires
modifications on all sync plugins.

-

[API] Drop osync_objtype_set_slowsync() and add parameter osync_bool *slowsync
to plugin connect()
http://www.opensync.org/ticket/1085

There were some ongoing discussion on IRC between Michael and Bjöern after
review i discovered a Bug inside OpenSync and the connect_done() handling
(which is fixed already). And to make things clear i plan to put this change
on the API break list.

-

[API] Common API interface pattern for list-implementations
http://www.opensync.org/ticket/975

Björn is working on that.

-

[API] size_t/unsigned int review and cleanup
http://www.opensync.org/ticket/974

This is currently up for takers - please start with public APIs. Internal APIs
we can fix later (after 0.39). This means review all headers which get
installed and parameter lists of functions which start with OSYNC_EXPORT.

-

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 ..)

-

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.

.......

That's all. I hope there is no further need for tickets in 0.39. All tickets
not related to API changes will get moved to 0.40. If you have any thing left
which needs to be fixed in 0.39 - please drop me a mail.

Best Regards,
Daniel

------------------------------------------------------------------------------
_______________________________________________
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...