It appears that Walkaround takes a snapshot and imports that, rather than processing the deltas, if
I'm reading it correctly.
On 2011-12-13 17:39, Yuri Z wrote:
You look how Walkaround handles the import. For example
That is the same conclusion I reached from looking at it when it was first
mentioned on this list.
This has the advantage of being quick for a one-time feature, but loses the
flexibility of processing all the raw deltas instead.
On Dec 14, 2011 3:24 PM, Thomas Leonard
What are possible advantages of building the wavelet from deltas?
Anyway, I think you can also look how WIAB reads the deltas from files at
https://github.com/apache/wave/blob/trunk/src/org/waveprotocol/box/server/persistence
specifically - FileDeltaCollection.readAppliedDelta
On Wed, Dec 14,
Walkaround's import feature currently indeed constructs a short fake
history rather than importing each delta.
The reasons for this are:
* Google Wave's APIs do not allow exporting deltas for user data
wavelets (read/unread/folder/archived information). For these, the
snapshot is all you get.
You look how Walkaround handles the import. For example
http://code.google.com/p/walkaround/source/browse/src/com/google/walkaround/wave/server/googleimport/conversion/WaveletHistoryConverter.java
and other classed in the package/package above
On Tue, Dec 13, 2011 at 5:02 PM, Thomas Leonard
Is an import feature likely to appear before wave.google.com becomes read-only? Import to Walkaround
seems to work (though it would take a long time to import all our waves by clicking all the import
buttons), but we'd prefer to import into a local WIAB instance, if possible.
Thanks,
On
I would advice to import them to a Walkaround instance just to be sure your
waves are safe.
On Wed, Dec 7, 2011 at 6:46 PM, Thomas Leonard
t...@it-innovation.soton.ac.uk wrote:
Is an import feature likely to appear before wave.google.com becomes
read-only? Import to Walkaround seems to work
I have an instance running at http://wiabexport.appspot.com which I
wrote a while ago. This uses the python interface to pull out the
wavelet raw deltas and offers them for download to you.
I never finished a script to convert to the delta/index file format
used by WIAB - due to the lack of
such as...?
On 18 May 2011 23:49, Yuri Z vega...@gmail.com wrote:
Yep, and some more things too.
2011/5/19 Zachary “Gamer_Z.” Yaro zmy...@gmail.com
IMHO better wave persistence and storage are needed before we should
consider mass importing from Gwave.
--Zachary “Gamer_Z.” Yaro
On Wed,
Like scalability. No point to let everybody to import a lot of waves into
WIAB server only to discover it's just too much for one machine to handle.
2011/5/19 Ali Lown a...@lown.me.uk
such as...?
On 18 May 2011 23:49, Yuri Z vega...@gmail.com wrote:
Yep, and some more things too.
Offtopic:
Has anyone tested what 1 machine can handle in terms of waves/users using WIAB?
Besides, I am only interested in having a very small (10 user) WIAB
system, so that wouldn't affect me, I just want to be able to import
my existing waves.
I have setup: wiabexport.appspot.com that
IMO, if wave import development is parallelizable with the rest of tasks, I
see no reason to forcibly block it, or to prevent any newcomer from doing
it.
While I agree that the most common case (that is, each of us importing our
Google Wave history into waveinabox.net) makes makes no sense,
Currently ~5 Online users/~700 waves would cause the server to become really
slow (on c1.medium Amazon EC2 machine).
The main reason for such poor performance is the current implementation of
search functionality. We are currently working on a patch to improve it
though. I think that after fixing
No one is blocking or preventing. It just that someone should write some
user friendly import tool.
2011/5/19 STenyaK sten...@gmail.com
IMO, if wave import development is parallelizable with the rest of tasks, I
see no reason to forcibly block it, or to prevent any newcomer from doing
it.
On the old waveprotocol site task list, this is still listed as waiting for
google to implement export.
Export has now been available for a while for waves, has any progress been
made on importing them?
The HTML option, actually provides the data in a JSON form, is there are
parser for this
Google Wave Data API was modified to allow to request the whole history of
the wave - which in effect allows to import it. But AFAIK no one is
working on a tool that would actually import the history into WIAB deltas
store.
2011/5/18 Ali Lown a...@lown.me.uk
On the old waveprotocol site task
Looking at the python interface: I can see the robot.fetch_wavelet
method, but that only returns a snapshot at that point in time.
How would I request the full history of the wave (wavelet?).
Ali
On 18 May 2011 20:51, Yuri Z vega...@gmail.com wrote:
Google Wave Data API was modified to allow
IMHO better wave persistence and storage are needed before we should
consider mass importing from Gwave.
--Zachary “Gamer_Z.” Yaro
On Wed, May 18, 2011 at 17:20, Soren Lassen sorenlas...@gmail.com wrote:
There's some documentation about the data export features in the Data API
here:
18 matches
Mail list logo
