Re: [Zope-dev] Zope3 on Google AppEngine

2008-06-02 Thread David Pratt
Interesting post. I am still not sure to what level I'll look to Google 
for app infrastructure. Seems to me there are too many restrictions on 
what you'd really be able to deploy and then you're stuck with married 
to what they've got for better or worse. On the other hand, Stripping 
zope to the minimum has certainly been an eye opener and certainly 
beneficial to get to a bare bones idea of what you could run with (with 
or without Google) though. Many thanks for sharing your efforts on this.


Regards,
David

Kapil Thangavelu wrote:

perhaps too late to help with the sprints, but i got zope3 running on
app engine last week http://zope3.appspot.com and
http://zope3.appspot.com/tests, and blogged about to
http://blog.kapilt.com

most of zope.app isn't useable due to persistence or containment and
security proxies, but page templates and the publisher work. some
fairly minor but pervasive changes (removing some deprecations/bbb
code) were needed, and to have space (1000 file limit) to actually
develop an application requires stripping the eggs of text and tests.
i ended up using the publisher support in zope.publisher (3.5.1+)
instead of ore.wsgiapp or lovely.nozodb as it presents a much more
minimal dependency set.

i'd like to see if i can get some form machinery going underneat the
1000 file limit, and publish a starter tarball for folks interested.

i'm uncertain long term what's viable, as their were a number of
changes needed, and how best to maintain them. if their suitable for
upstream into the zope repository, or just done again for separate
releases as gae variant of z3.

cheers,

kapil

On 5/22/08, Jodok Batlogg [EMAIL PROTECTED] wrote:

Hi,

 Next week Lovely will be sprinting in New York/San Francisco to get the
Zope3 framework and the first applications running on Google AppEngine.
You're welcome to join us.
 Google AppEngine is a perfect match to the transition we at Lovely Systems
made during the last 12 month in stealth mode.
 We're using heavily WSGI and are replacing ZODB within most of our
applications.
 Tomorrow we're leaving to New York visiting our friend reco. dobee and I
will be working on getting the component architecture running on AppEngine.
 Later next week we'll fly to San Francisco to attend Google I/O and get
even more insight to the technology.
 We're open to release lovely.nozodb and the related components in near
future, as usual - just some polishing missing…
 Please drop me a note ([EMAIL PROTECTED], batlogg on skype/AIM) or
give me a call (+43 664 9636963) if you want to join us.

 jodok
 --
 Lovely Systems, Partner

 phone: +43 5572 908060, fax: +43 5572 908060-77
 Schmelzhütterstraße 26a, 6850 Dornbirn, Austria
 _

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce

 http://mail.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope3 on Google AppEngine

2008-06-01 Thread Kapil Thangavelu
perhaps too late to help with the sprints, but i got zope3 running on
app engine last week http://zope3.appspot.com and
http://zope3.appspot.com/tests, and blogged about to
http://blog.kapilt.com

most of zope.app isn't useable due to persistence or containment and
security proxies, but page templates and the publisher work. some
fairly minor but pervasive changes (removing some deprecations/bbb
code) were needed, and to have space (1000 file limit) to actually
develop an application requires stripping the eggs of text and tests.
i ended up using the publisher support in zope.publisher (3.5.1+)
instead of ore.wsgiapp or lovely.nozodb as it presents a much more
minimal dependency set.

i'd like to see if i can get some form machinery going underneat the
1000 file limit, and publish a starter tarball for folks interested.

i'm uncertain long term what's viable, as their were a number of
changes needed, and how best to maintain them. if their suitable for
upstream into the zope repository, or just done again for separate
releases as gae variant of z3.

cheers,

kapil

On 5/22/08, Jodok Batlogg [EMAIL PROTECTED] wrote:
 Hi,

  Next week Lovely will be sprinting in New York/San Francisco to get the
 Zope3 framework and the first applications running on Google AppEngine.
 You're welcome to join us.
  Google AppEngine is a perfect match to the transition we at Lovely Systems
 made during the last 12 month in stealth mode.
  We're using heavily WSGI and are replacing ZODB within most of our
 applications.
  Tomorrow we're leaving to New York visiting our friend reco. dobee and I
 will be working on getting the component architecture running on AppEngine.
  Later next week we'll fly to San Francisco to attend Google I/O and get
 even more insight to the technology.
  We're open to release lovely.nozodb and the related components in near
 future, as usual - just some polishing missing…
  Please drop me a note ([EMAIL PROTECTED], batlogg on skype/AIM) or
 give me a call (+43 664 9636963) if you want to join us.

  jodok
  --
  Lovely Systems, Partner

  phone: +43 5572 908060, fax: +43 5572 908060-77
  Schmelzhütterstraße 26a, 6850 Dornbirn, Austria
  _
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope3 on Google AppEngine

2008-05-30 Thread Hermann Himmelbauer
Am Sonntag, 25. Mai 2008 13:32 schrieb Andreas Jung:
 --On 24. Mai 2008 15:44:01 +0200 Hermann Himmelbauer [EMAIL PROTECTED] 
 wrote:
   I currently use
  SQLAlchemy,  but it seems that transactions are managed on the RDB-level
  only, which means  that the object state is not in the transaction scope.

 Huh? If you use one of the integration framework for sqlalchemy-within-zope
 then SQLAlchemy is fully integrated with the Zope transaction system.

In my application, I use zope.sqlalchemy and I load my objects from the 
database via SA. These objects have interfaces and are related to SA tables 
via mappers. If I now change such an SA object and do a transaction.abort(), 
a database rollback is issued, however, SA does not restore the object state.

For common cases, this is no problem, as in my application, a transaction 
correlates with a HTTP request/response span, and if objects at the end of 
the operation are restored or not is of no interest (as data is stored in the 
database and the objects are discarded); what counts is that the database 
holds the right data.

Nevertheless I have cases (e.g. in testing scenarios) where it makes sense to 
manually issue a transaction.abort(). In this case I have to reload the 
objects from the database in order to be consistent with the database.

But maybe there's some magic class from an additional z3c package I can 
inherit my classes from, which solves this issue?

Best Regards,
Hermann

-- 
[EMAIL PROTECTED]
GPG key ID: 299893C7 (on keyservers)
FP: 0124 2584 8809 EF2A DBF9  4902 64B4 D16B 2998 93C7
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope3 on Google AppEngine

2008-05-25 Thread Andreas Jung



--On 24. Mai 2008 15:44:01 +0200 Hermann Himmelbauer [EMAIL PROTECTED] wrote:




 I currently use
SQLAlchemy,  but it seems that transactions are managed on the RDB-level
only, which means  that the object state is not in the transaction scope.


Huh? If you use one of the integration framework for sqlalchemy-within-zope 
then SQLAlchemy is fully integrated with the Zope transaction system.


Andreas



pgpbhiBAcII26.pgp
Description: PGP signature
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope3 on Google AppEngine

2008-05-25 Thread Hermann Himmelbauer
Am Freitag, 23. Mai 2008 18:19 schrieb David Pratt:
 Hi Jodok. I had looked at storm a while back but the zope integration
 seemed to lack any relationship with zope schemas.  I guess it is
 possible to define a zope schema that is not persisted and create the
 tables from it. It did not seem to me a good way of using CA. How are
 you managing this part of things.

 I Haven't worked with bigtable yet myself but assume the transactional
 semantics would be a challenge since I am not sure how quickly the data
 gets to the storage. This is interesting stuff in any case.

Very interesting, indeed. Does this mean that one can basically create classes 
that inherit from some class like persistent.Persistent and data is then 
simply stored in a RDB instead of ZODB?

What I'm curious is how transactions are managed; I currently use SQLAlchemy, 
but it seems that transactions are managed on the RDB-level only, which means 
that the object state is not in the transaction scope.

Another issue is data migration, which requires changes in the database model 
(altering tables etc.), so this might be also quite challenging.

Best Regards,
Hermann

-- 
[EMAIL PROTECTED]
GPG key ID: 299893C7 (on keyservers)
FP: 0124 2584 8809 EF2A DBF9  4902 64B4 D16B 2998 93C7
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope3 on Google AppEngine

2008-05-23 Thread David Pratt
Hi Jodok. I had looked at storm a while back but the zope integration 
seemed to lack any relationship with zope schemas.  I guess it is 
possible to define a zope schema that is not persisted and create the 
tables from it. It did not seem to me a good way of using CA. How are 
you managing this part of things.


I Haven't worked with bigtable yet myself but assume the transactional 
semantics would be a challenge since I am not sure how quickly the data 
gets to the storage. This is interesting stuff in any case.


Regards,
David

Jodok Batlogg wrote:

On Thu, May 22, 2008 at 4:53 PM, David Pratt [EMAIL PROTECTED] wrote:

Hi Jodok. Sounds interesting. Curious what you are replacing ZODB with. Are
you using its interfaces to Relstorage / other ZODB backend, an ORM to map
direct to rdb, or other database. Many thanks.


right now we're using storm.
for the application we plan to port first it seems like bigtable fits perfect.
during the next week we won't focus on the storage layer, but more on
getting the C-based things running.
the other part - lovely.nozodb (zope3 without zodb, utility
registrations,...) is almost done and just needs some polishing.

jodok


Regards,
David

Jodok Batlogg wrote:

Hi,

Next week Lovely will be sprinting in New York/San Francisco to get the
Zope3 framework and the first applications running on Google AppEngine.
You're welcome to join us.
Google AppEngine is a perfect match to the transition we at Lovely Systems
made during the last 12 month in stealth mode.
We're using heavily WSGI and are replacing ZODB within most of our
applications.
Tomorrow we're leaving to New York visiting our friend reco. dobee and I
will be working on getting the component architecture running on AppEngine.
Later next week we'll fly to San Francisco to attend Google I/O and get
even more insight to the technology.
We're open to release lovely.nozodb and the related components in near
future, as usual - just some polishing missing…
Please drop me a note ([EMAIL PROTECTED], batlogg on skype/AIM) or
give me a call (+43 664 9636963) if you want to join us.

jodok
--
Lovely Systems, Partner

phone: +43 5572 908060, fax: +43 5572 908060-77
Schmelzhütterstraße 26a, 6850 Dornbirn, Austria

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )





___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope3 on Google AppEngine

2008-05-22 Thread David Pratt
Hi Jodok. Sounds interesting. Curious what you are replacing ZODB with. 
Are you using its interfaces to Relstorage / other ZODB backend, an ORM 
to map direct to rdb, or other database. Many thanks.


Regards,
David

Jodok Batlogg wrote:

Hi,

Next week Lovely will be sprinting in New York/San Francisco to get the 
Zope3 framework and the first applications running on Google AppEngine. 
You’re welcome to join us.
Google AppEngine is a perfect match to the transition we at Lovely 
Systems made during the last 12 month in “stealth mode”.
We’re using heavily WSGI and are replacing ZODB within most of our 
applications.
Tomorrow we’re leaving to New York visiting our friend reco. dobee and I 
will be working on getting the component architecture running on AppEngine.
Later next week we’ll fly to San Francisco to attend Google I/O and get 
even more insight to the technology.
We’re open to release lovely.nozodb and the related components in near 
future, as usual - just some polishing missing…
Please drop me a note ([EMAIL PROTECTED], batlogg on skype/AIM) or 
give me a call (+43 664 9636963) if you want to join us.


jodok
--
Lovely Systems, Partner

phone: +43 5572 908060, fax: +43 5572 908060-77
Schmelzhütterstraße 26a, 6850 Dornbirn, Austria

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope3 on Google AppEngine

2008-05-22 Thread Jodok Batlogg
On Thu, May 22, 2008 at 4:53 PM, David Pratt [EMAIL PROTECTED] wrote:
 Hi Jodok. Sounds interesting. Curious what you are replacing ZODB with. Are
 you using its interfaces to Relstorage / other ZODB backend, an ORM to map
 direct to rdb, or other database. Many thanks.

right now we're using storm.
for the application we plan to port first it seems like bigtable fits perfect.
during the next week we won't focus on the storage layer, but more on
getting the C-based things running.
the other part - lovely.nozodb (zope3 without zodb, utility
registrations,...) is almost done and just needs some polishing.

jodok


 Regards,
 David

 Jodok Batlogg wrote:

 Hi,

 Next week Lovely will be sprinting in New York/San Francisco to get the
 Zope3 framework and the first applications running on Google AppEngine.
 You're welcome to join us.
 Google AppEngine is a perfect match to the transition we at Lovely Systems
 made during the last 12 month in stealth mode.
 We're using heavily WSGI and are replacing ZODB within most of our
 applications.
 Tomorrow we're leaving to New York visiting our friend reco. dobee and I
 will be working on getting the component architecture running on AppEngine.
 Later next week we'll fly to San Francisco to attend Google I/O and get
 even more insight to the technology.
 We're open to release lovely.nozodb and the related components in near
 future, as usual - just some polishing missing…
 Please drop me a note ([EMAIL PROTECTED], batlogg on skype/AIM) or
 give me a call (+43 664 9636963) if you want to join us.

 jodok
 --
 Lovely Systems, Partner

 phone: +43 5572 908060, fax: +43 5572 908060-77
 Schmelzhütterstraße 26a, 6850 Dornbirn, Austria

 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 http://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope3 on Google AppEngine

2008-05-22 Thread Jodok Batlogg
On Thu, May 22, 2008 at 6:34 PM, Roger Ineichen [EMAIL PROTECTED] wrote:
 Hi jodok

 Betreff: [Zope-dev] Zope3 on Google AppEngine

 Hi,

 Next week Lovely will be sprinting in New York/San Francisco
 to get the Zope3 framework and the first applications running
 on Google AppEngine. You're welcome to join us.
 Google AppEngine is a perfect match to the transition we at
 Lovely Systems made during the last 12 month in stealth mode.
 We're using heavily WSGI and are replacing ZODB within most
 of our applications.
 Tomorrow we're leaving to New York visiting our friend reco.
 dobee and I will be working on getting the component
 architecture running on AppEngine.
 Later next week we'll fly to San Francisco to attend Google
 I/O and get even more insight to the technology.
 We're open to release lovely.nozodb and the related
 components in near future, as usual - just some polishing
 missing… Please drop me a note ([EMAIL PROTECTED],
 batlogg on skype/AIM) or give me a call (+43 664 9636963) if
 you want to join us.

 Sounds very interesting. But take care, not every customer likes
 to have his data on such a share. Think about what could happen
 if google get a negative touch in the future. Probably you must
 be able to switch very fast from google to a none shared DB
 if customers become a bad feeling about it.

yes, you're right. i don't think any of our customers feels
comfortable running his portal on AppEngine. But as our applications
are utilizing multiple webservices (e.g. commenting,
authentication,...) these webservices could be run on appengine.

and yes again. unfortunately there is no open source / non-google DB
application implementation so far. we keep this in mind.

jodok


 But I guess that's another topic. Anyway, sounds really great!

 Regards
 Roger Ineichen

 jodok
 --
 Lovely Systems, Partner

 phone: +43 5572 908060, fax: +43 5572 908060-77
 Schmelzhütterstraße 26a, 6850 Dornbirn, Austria

 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 http://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  ** (Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
  http://mail.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )