I am about to write a tender. The solution might be a PHP based CMS. Later I might want to integrate an ASP.NET framework and make it look like one site.
我即将写一份招标书。解决方案可能是基于PHP的CMS。后来我可能想要集成ASP.NET框架并使其看起来像一个站点。
- What features would make this relatively easy.
- Would OpenId and similar make a difference?
- In the PHP world Joomla is supposed to be more integrative than Druapal. What are the important differences here?
- Are there spesific frameworks in ASP.NET, Python or Ruby that are more open to integration than others?
什么功能会使这相对容易。
OpenId和类似的东西会有所不同吗?
在PHP世界中,Joomla应该比Druapal更具整合性。这里有什么重要的区别?
ASP.NET,Python或Ruby中的特定框架是否比其他框架更易于集成?
2 个解决方案
#1
The most important thing is going to be putting as much of the look-and-feel in a format that can be shared by any platforms. That means you should develop a standard set of CSS files and (X)HTML files which can be imported (or directly presented) in any of those platform options. Think about it as writing a dynamic library that can be loaded by different programs.
最重要的是将所有外观放在可以由任何平台共享的格式中。这意味着您应该开发一组标准的CSS文件和(X)HTML文件,这些文件可以在任何这些平台选项中导入(或直接呈现)。把它想象成编写一个可以由不同程序加载的动态库。
Using OpenID for authentication, if all of your platform options support it, would be nice, but remember that each platform is going to require additional user metadata be stored for each user (preferences, last login, permissions/roles, etc) which you'll still have to wrangle between them. OpenID only solves the authentication problem, not the authorization or preferences problems.
使用OpenID进行身份验证,如果您的所有平台选项都支持它,那就太好了,但请记住,每个平台都需要为每个用户(首选项,上次登录,权限/角色等)存储额外的用户元数据。我们仍然要在他们之间争吵。 OpenID仅解决身份验证问题,而不是授权或首选项问题。
Lastly, since there are so many options, I would stick to cross-platform solutions. That will leave you the most options going forward. There's no compelling advantage IMHO to using ASP.NET if there's a chance you may one day integrate with other systems or move to another system.
最后,由于有很多选择,我会坚持使用跨平台解决方案。这将为您提供最多的选择。如果有可能有一天你可能有一天与其他系统集成或转移到另一个系统,那么使用ASP.NET就没有令人信服的优势。
#2
I think that most important thing is to choose the right server. The server needs to have adequate modules. Apache would be good choice as it supports all that you want, including mod_aspnet (which I didn't test, but many people say it works).
我认为最重要的是选择合适的服务器。服务器需要有足够的模块。 Apache将是一个很好的选择,因为它支持你想要的所有东西,包括mod_aspnet(我没有测试,但很多人说它有效)。
If you think asp.net integration is certanly going to come, I would choose Windows as OS as it will certanly be easier.
如果您认为asp.net集成将会出现,我会选择Windows作为操作系统,因为它会更容易。
You could also install reverse proxy that would decide which server to render content based on request - if user request aspx page, proxy will connect to the IIS and windoze page, if it asks for php it can connect to other server. The problem with this approach is shared memory & state, which could be solved with carefull design to support this - like shared database holding all state information and model data....
您还可以安装反向代理,根据请求决定哪个服务器呈现内容 - 如果用户请求aspx页面,代理将连接到IIS和windoze页面,如果它要求php它可以连接到其他服务器。这种方法的问题是共享内存和状态,可以通过精心设计来解决这个问题 - 就像共享数据库一样,包含所有状态信息和模型数据....
OpenID doesn't make a difference - there are libs for any framework you choose.
OpenID没有什么区别 - 你选择的任何框架都有libs。
#1
The most important thing is going to be putting as much of the look-and-feel in a format that can be shared by any platforms. That means you should develop a standard set of CSS files and (X)HTML files which can be imported (or directly presented) in any of those platform options. Think about it as writing a dynamic library that can be loaded by different programs.
最重要的是将所有外观放在可以由任何平台共享的格式中。这意味着您应该开发一组标准的CSS文件和(X)HTML文件,这些文件可以在任何这些平台选项中导入(或直接呈现)。把它想象成编写一个可以由不同程序加载的动态库。
Using OpenID for authentication, if all of your platform options support it, would be nice, but remember that each platform is going to require additional user metadata be stored for each user (preferences, last login, permissions/roles, etc) which you'll still have to wrangle between them. OpenID only solves the authentication problem, not the authorization or preferences problems.
使用OpenID进行身份验证,如果您的所有平台选项都支持它,那就太好了,但请记住,每个平台都需要为每个用户(首选项,上次登录,权限/角色等)存储额外的用户元数据。我们仍然要在他们之间争吵。 OpenID仅解决身份验证问题,而不是授权或首选项问题。
Lastly, since there are so many options, I would stick to cross-platform solutions. That will leave you the most options going forward. There's no compelling advantage IMHO to using ASP.NET if there's a chance you may one day integrate with other systems or move to another system.
最后,由于有很多选择,我会坚持使用跨平台解决方案。这将为您提供最多的选择。如果有可能有一天你可能有一天与其他系统集成或转移到另一个系统,那么使用ASP.NET就没有令人信服的优势。
#2
I think that most important thing is to choose the right server. The server needs to have adequate modules. Apache would be good choice as it supports all that you want, including mod_aspnet (which I didn't test, but many people say it works).
我认为最重要的是选择合适的服务器。服务器需要有足够的模块。 Apache将是一个很好的选择,因为它支持你想要的所有东西,包括mod_aspnet(我没有测试,但很多人说它有效)。
If you think asp.net integration is certanly going to come, I would choose Windows as OS as it will certanly be easier.
如果您认为asp.net集成将会出现,我会选择Windows作为操作系统,因为它会更容易。
You could also install reverse proxy that would decide which server to render content based on request - if user request aspx page, proxy will connect to the IIS and windoze page, if it asks for php it can connect to other server. The problem with this approach is shared memory & state, which could be solved with carefull design to support this - like shared database holding all state information and model data....
您还可以安装反向代理,根据请求决定哪个服务器呈现内容 - 如果用户请求aspx页面,代理将连接到IIS和windoze页面,如果它要求php它可以连接到其他服务器。这种方法的问题是共享内存和状态,可以通过精心设计来解决这个问题 - 就像共享数据库一样,包含所有状态信息和模型数据....
OpenID doesn't make a difference - there are libs for any framework you choose.
OpenID没有什么区别 - 你选择的任何框架都有libs。