1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
<!--
-
- This file is part of the OpenLink Software Virtuoso Open-Source (VOS)
- project.
-
- Copyright (C) 1998-2024 OpenLink Software
-
- This project is free software; you can redistribute it and/or modify it
- under the terms of the GNU General Public License as published by the
- Free Software Foundation; only version 2 of the License, dated June 1991.
-
- This program is distributed in the hope that it will be useful, but
- WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
- General Public License for more details.
-
- You should have received a copy of the GNU General Public License along
- with this program; if not, write to the Free Software Foundation, Inc.,
- 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
-
-
-->
<?xml version="1.0" encoding="ISO-8859-1"?>
<refentry id="blog-bridge">
<refmeta>
<refentrytitle>Blogger Bridge</refentrytitle>
<refmiscinfo>tutorial</refmiscinfo>
</refmeta>
<refnamediv>
<refname>Weblog Bridge</refname>
<refpurpose>Synchronizing local Blog storage with multiple Blog servers via Blogger APIs</refpurpose>
</refnamediv>
<refsect1 id="blogbridgea">
<title>Example</title>
<itemizedlist mark="bullet">
<listitem>The demo shows a way to replicate a blog messages to multiple destinations.</listitem>
<listitem>The destinations are configurable via "Blogger Brigde" link of blogging page.</listitem>
<listitem>A destination server *MUST* support one of following APIs: blogger, metaWeblog or Movable Type.</listitem>
<listitem>To select a blog from target the URL, Username and password must be entered before "Fetch" button clicked.</listitem>
<listitem>You may choose one of BLOGs listed in pop-up window.</listitem>
<listitem>Once you have defined a Bridge target, you can verify the bridging with post via main page.</listitem>
<listitem>Note that bridge will post the messages with it's own application key ; so that message will not be replicated. if you are choosed the same server and blog, messages will appear twise as original will be replicated.</listitem>
</itemizedlist>
</refsect1>
</refentry>
|
