2013-05-27 50 views
-1

我的服務器正在運行RHEL 6.2,我正在使用Python 2.7,Google App Engine運行以允許基於Web的Python應用程序(https://developers.google.com/appengine/docs/python/gettingstartedpython27/)。當我在紅帽企業Linux中使用Google App Engine時,是否違反許可條款?

現在當最終用戶瀏覽頁面並使用瀏覽器的應用程序(我的服務器中的後端我使用Python + Google App Engine)時。

我所屬的許可證條款是什麼? 它是GPL或沒有或我是否可以自由使用(像任何網站..)或我落在一些許可條款時 - 我曾經會使用任何種類的谷歌應用引擎相關..?

有什麼想法?

GOOGLE APP ENGINE SDK 
===================== 
Copyright 2008 Google Inc. 
All rights reserved. 

Licensed under the Apache License, Version 2.0 (the "License"); 
you may not use this file except in compliance with the License. 
You may obtain a copy of the License at 

    http://www.apache.org/licenses/LICENSE-2.0 

Unless required by applicable law or agreed to in writing, software 
distributed under the License is distributed on an "AS IS" BASIS, 
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
See the License for the specific language governing permissions and 
limitations under the License. 


DJANGO FRAMEWORK 
================ 
Copyright (c) 2005, the Lawrence Journal-World 
All rights reserved. 

Redistribution and use in source and binary forms, with or without modification, 
are permitted provided that the following conditions are met: 

    1. Redistributions of source code must retain the above copyright notice, 
     this list of conditions and the following disclaimer. 

    2. Redistributions in binary form must reproduce the above copyright 
     notice, this list of conditions and the following disclaimer in the 
     documentation and/or other materials provided with the distribution. 

    3. Neither the name of Django nor the names of its contributors may be used 
     to endorse or promote products derived from this software without 
     specific prior written permission. 

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR 
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON 
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS 
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 


WebOb 
====== 

Copyright (c) 2007 Ian Bicking and Contributors 

Permission is hereby granted, free of charge, to any person obtaining 
a copy of this software and associated documentation files (the 
"Software"), to deal in the Software without restriction, including 
without limitation the rights to use, copy, modify, merge, publish, 
distribute, sublicense, and/or sell copies of the Software, and to 
permit persons to whom the Software is furnished to do so, subject to 
the following conditions: 

The above copyright notice and this permission notice shall be 
included in all copies or substantial portions of the Software. 

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF 
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND 
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE 
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION 
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION 
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 


PyYaml 
======= 
Copyright (c) 2006 Kirill Simonov 

Permission is hereby granted, free of charge, to any person obtaining a copy of 
this software and associated documentation files (the "Software"), to deal in 
the Software without restriction, including without limitation the rights to 
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies 
of the Software, and to permit persons to whom the Software is furnished to do 
so, subject to the following conditions: 

The above copyright notice and this permission notice shall be included in all 
copies or substantial portions of the Software. 

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 
SOFTWARE. 


cacerts 
======= 
Version: MPL 1.1/GPL 2.0/LGPL 2.1 

The contents of this file are subject to the Mozilla Public License Version 
1.1 (the "License"); you may not use this file except in compliance with 
the License. You may obtain a copy of the License at 
http://www.mozilla.org/MPL/ 

Software distributed under the License is distributed on an "AS IS" basis, 
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License 
for the specific language governing rights and limitations under the 
License. 

The Original Code is the Netscape security libraries. 

The Initial Developer of the Original Code is 
Netscape Communications Corporation. 
Portions created by the Initial Developer are Copyright (C) 1994-2000 
the Initial Developer. All Rights Reserved. 

Contributor(s): 

Alternatively, the contents of this file may be used under the terms of 
either the GNU General Public License Version 2 or later (the "GPL"), or 
the GNU Lesser General Public License Version 2.1 or later (the "LGPL"), 
in which case the provisions of the GPL or the LGPL are applicable instead 
of those above. If you wish to allow use of your version of this file only 
under the terms of either the GPL or the LGPL, and not to allow others to 
use your version of this file under the terms of the MPL, indicate your 
decision by deleting the provisions above and replace them with the notice 
and other provisions required by the GPL or the LGPL. If you do not delete 
the provisions above, a recipient may use your version of this file under 
the terms of any one of the MPL, the GPL or the LGPL. 
+2

你的問題不是很清楚。我認爲App Engine是在Google服務器上運行的,並且您在那裏上傳應用程序。你正在運行你自己的App Engine實例嗎?你在哪裏得到它? – kirelagin

+0

@kirelagin:Google App Engine'dev_appserver.py'運行在我的RHEL 6.2中,而不是在Google服務器上,我的用戶將瀏覽我的服務器,而不是Google服務器。但是,我聽說過,當我使用Google App Engine時,我必須獲得許可或支付Google費用?即使所有運行在我的服務器? – YumYumYum

+0

這裏下載谷歌應用程序引擎很容易:https://developers.google.com/appengine/downloads – YumYumYum

回答

2

好的,我會嘗試猜測。你正在運行一個開發服務器嗎?正如我所看到的,它是Apache許可的,所以你可以自由地做任何你想做的事情,包括在你的服務器上運行它,並讓其他人使用託管在它上面的Web應用程序。

現在一切都取決於特定應用程序的許可條款。如果它的許可證允許你運行它,你可以運行它。而已。

說到GPL,它有一個有趣的缺陷:當你運行一個Web應用程序時,你不會分發應用程序,因此你可以克服GPL限制。這就是爲什麼AGPL存在。

更新:您在評論中提到Terms of Service。基本上你不應該關心它,因爲你有一個軟件(dev_appserver),你有它的許可證,這個許可證明確允許你做任何(幾乎)你想要的。

如果你真的擔心這個,你看在4.4:

的服務組件

開源軟件許可證發佈 下開源許可構成單獨的書面協議。 開放源代碼軟件列在文檔中。有限的 程度的開放源代碼軟件許可明確取代本 協議,開放源代碼的許可,而不是客戶應遵守 與谷歌的協議對具體包括開源組件的服務,或者使用本服務的 (如可能適用)。

+0

但我不明白爲什麼我們必須支付,即使我們使用我們的服務器,我們的源代碼,我們的一切,我們的設置。爲什麼仍然需要向谷歌支付使用Google應用引擎的費用? – YumYumYum

+1

你在哪裏看到有關付款的事情? – kirelagin

+0

此處https://developers.google.com/appengine/terms>選項3 – YumYumYum

相關問題