Re: [SyncEvolution] New backend for integration with web applications
Dear Patrick,
On Tue, 1 Dec 2009, Patrick Ohly wrote:
Given your complete lack of questions, may I assume that you found
the
available material sufficient to accomplish what you wanted to do (okay,
except for the questions that your raised below)?
Yes, I did. The most complicated part was the integration into the
autoconf/automake configuration :-) The FileSyncSource.* was an excellent
point to start.
There are existing methods as well as unimplemented ideas for making
this more flexible. Let me know if you want to know more and we can dive
more deeply into this.
As our application will exchange vcards and icals not only by means of
SyncML, but e. g. also by mail, we had to build the flexibility inside of
the application. Therefore I'd like to turn off any conversion or mapping.
If it compiles for you, it should compile for us, once we install
the
necessary development files for the new library dependencies.
On ubuntu or Debian: apt-get install libxmlrpc-c3-dev
That depends on a bit on how often you want to send updates. If it
is
infrequent, then "git am-format" from your private repo and attaching
the result to a Bugzilla entry is the preferred method.
Ok, I'll do that.
http://bugzilla.moblin.org/waiver.html
Would that be acceptable for you?
Yes, absolutely.
My own goal was to only have such a waiver or transfer for core code
and
let backends be contributed under any suitable license. Is that
something that I should push for? I can't guarantee that it'll get
through inside Intel, but I can certainly try.
No, the waiver above is fine for me.
Right now all that we have is plain ASCII. There is an issue about
using
a richer format for user documentation:
http://bugzilla.moblin.org/show_bug.cgi?id=4633
Ok, my documentation is currently in our company-wide wiki, so it's quite
easy to write an ASCII documentation.
Right now, the environment variable CLIENT_TEST_EVOLUTION_SOURCE can
be
set to a certain prefix, like "file:///tmp/test_". The name of the data
(ical20, vcard30, ...) and the numbers 1 and 2 are appended to form
unique evolutionsource values. For example, with the prefix
above, /tmp/test_ical20_1 and /tmp/test_ical20_2 would be used for tests
which require two local databases.
Ok, I see. I'll have a look on that, this also means to set up two users
in the web application, etc.
I'll create the bugzilla report right after writing the README file.
Have a nice day,
Franz
--
NEUE MOBILNUMMER: +43 660 4859550
Franz Knipp, Dipl.-Ing.
---------------------------------------------------------------------
knipp(a)m-otion.com
+43 660 4859550
https://www.xing.com/profile/Franz_Knipp
---------------------------------------------------------------------
m-otion GmbH
Favoritenstr 4-6/III, 1040 Wien
+43 1 205705 (Fax 99)
---------------------------------------------------------------------
www.m-otion.com