AppRocket 2.0.0 is now available

[Kurt Daal]

Good news today - after some quiet period, AppRocket has finally got
it's long-due update.

The biggest change in this update is parallel replication of entities.
In earlier releases all entities where processed in a row, which in
real life didn't work that well. Now AppRocket has a fresh new multi-
threaded engine under the hood which gives huge perfomance boosts if
your application contain more than one active entity.

Also this update contains a bunch of bug-fixes. Before release, it has
been extensively utilized in couple live projects and appears to be
stable and rock-solid.

[Waleed Abdulla]

Thanks Kurt. It works great. Much appreciated. 

One note about the documentation on the project home page on Google Code. It might save new users some time if it mentions that there should be two copies of the rocket folder, one on the appengine project and one on the mysql box, and that they should have identical copies of config.py. When I started, I anticipated seeing two folders, one for each side. But then I guessed that it must be the same folder in both places, but there was no assurance in the documentation. It's not until you go with that assumption and it works that you know you guessed right. 

Awesome project. Thanks again. 

Waleed

--

You received this message because you are subscribed to the Google Groups "AppRocket" group.
To post to this group, send email to appr...@googlegroups.com.
To unsubscribe from this group, send email to approcket+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/approcket?hl=en.

[Kurt Daal]

A couple more details in my blog: http://kurtdaal.com/post/266240513/approcket-2-0-0-has-arrived

[Kurt Daal]

I usually have just one shared folder for both, but anyways it's a
good point.

On Dec 2, 10:35 am, Waleed Abdulla <wal...@ninua.com> wrote:
> Thanks Kurt. It works great. Much appreciated.
>
> One note about the documentation on the project home page on Google Code. It
> might save new users some time if it mentions that there should be two
> copies of the rocket folder, one on the appengine project and one on the
> mysql box, and that they should have identical copies of config.py. When I
> started, I anticipated seeing two folders, one for each side. But then I
> guessed that it must be the same folder in both places, but there was no
> assurance in the documentation. It's not until you go with that assumption
> and it works that you know you guessed right.
>
> Awesome project. Thanks again.
>
> Waleed
>

> On Tue, Dec 1, 2009 at 6:52 AM, Kurt Daal <kurt.d...@gmail.com> wrote:
> > Good news today - after some quiet period, AppRocket has finally got
> > it's long-due update.
>
> > The biggest change in this update is parallel replication of entities.
> > In earlier releases all entities where processed in a row, which in
> > real life didn't work that well. Now AppRocket has a fresh new multi-
> > threaded engine under the hood which gives huge perfomance boosts if
> > your application contain more than one active entity.
>
> > Also this update contains a bunch of bug-fixes. Before release, it has
> > been extensively utilized in couple live projects and appears to be
> > stable and rock-solid.
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "AppRocket" group.
> > To post to this group, send email to appr...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > approcket+...@googlegroups.com<approcket%2Bunsu...@googlegroups.com>
> > .

[Waleed Abdulla]

I usually have just one shared folder for both, but anyways it's a
good point.

I guessed so. My use case is different. I have a Web app on php/mysql and I've reached a point where I'm spending a lot of time on scaling and optimization, so I decided to move parts of the app to the app engine where it will scale easier. There is data that both the php and the app engine parts need, so I'm going to use App Rocket to keep replicate all updates on mysql to app engine. So in my case, one folder lives on a mysql box at a hosting company and the other is part of my app engine app in production.