You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/04/08 23:00:15 UTC
[jira] Updated: (TAP5-634) Google App Engine Support: ability to
disable code that creates new threads
[ https://issues.apache.org/jira/browse/TAP5-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-634:
--------------------------------------
Description:
Right off the bat, the restriction in GAE that no threads be created will affect a few, small sections of Tapestry.
In the larger scheme of things, a tapestry-googleappengine library may require a few things:
- Make the GAE services (such as UserService) injectable
- Support for JDO (much like tapestry-hibernate, today)
- Other, unforseen
Also, depending on the license of GAE (and availabilty through Maven) may need to host such a library at Tapestry360.
was:
Right off the bat, the restriction in GAE that no threads be created will affect a few, small sections of Tapestry.
In the larger scheme of things, a tapestry-googleappengine library may require a few things:
- Make the GAA services (such as UserService) injectable
- Support for JDO (much like tapestry-hibernate, today)
- Other, unforseen
Also, depending on the license of GAE (and availabilty through Maven) may need to host such a library at Tapestry360.
Summary: Google App Engine Support: ability to disable code that creates new threads (was: Google App Engine Support: disable code that creates new threads)
> Google App Engine Support: ability to disable code that creates new threads
> ---------------------------------------------------------------------------
>
> Key: TAP5-634
> URL: https://issues.apache.org/jira/browse/TAP5-634
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core, tapestry-ioc
> Affects Versions: 5.1.0.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> Right off the bat, the restriction in GAE that no threads be created will affect a few, small sections of Tapestry.
> In the larger scheme of things, a tapestry-googleappengine library may require a few things:
> - Make the GAE services (such as UserService) injectable
> - Support for JDO (much like tapestry-hibernate, today)
> - Other, unforseen
> Also, depending on the license of GAE (and availabilty through Maven) may need to host such a library at Tapestry360.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.