为什么Web编程具有挑战性和不同性 [英] Why Web Programming is so Challenging and Different
问题描述
我被聘请去找我的前客户并在ASP.NET上培训他们的员工
程序员。这些人只有大型机，MS Access，SQL
服务器和VB6桌面应用程序开发经验（绝对没有HTML或Web应用程序经验）。
在进入任何代码之前，我认为让它们变得很重要
了解
Web应用程序所带来的根本差异和独特挑战开发（独立于任何特定应用程序
技术; asp，php等）。
以下是我计划的一些独特挑战（或基本原理）尽早报道
。我很感激您对此列表的反馈 - 请让我知道
您认为应该包含的任何我错过的内容。
1. HTTP（3 - 握手等）
2.请求/响应模型
3.状态管理
4.客户端逻辑和脚本与服务器端。
5. HTML和CSS（内容和布局与样式）
6.浏览器的变化和限制
谢谢！
-F
我认为第3点必须被夯实回家。重点是
无连接状态管理技术。这样做。
" Frankie" <钽****** @ BeanTown.org>在消息中写道
新闻：#X ************* @ tk2msftngp13.phx.gbl ...我被录用了去找我的一个前客户，并在ASP.NET上培训他们的员工
程序员。这些人只有大型机，MS Access，SQL
服务器和VB6桌面应用程序开发经验（绝对没有HTML或Web应用程序体验
）。
在跳入任何代码之前我认为让他们了解Web应用程序开发所带来的根本差异和独特挑战是非常重要的（独立于任何特定的应用程序技术; asp，php等） 。
以下是我计划在早期介绍的一些独特挑战（或基本原则）。我很感激您对此列表的反馈 - 请让我知道
您认为应该包含的任何我错过的内容。
1. HTTP（三次握手等）
2.请求/响应模型
3.状态管理
4.客户端逻辑和脚本与服务器端。
5. HTML和CSS（内容和布局vs 。样式）
6.浏览器的变化和限制
谢谢！
-F
我相信你已经击中了biggies。在列表中。特别是，解释HTTP请求/响应
模型的无状态性质以及ASP.Net IHttpHandler接口和派生类（exp。
System.Web.UI.Page）旨在处理它。我还要完整地解释一下System.Web.UI.Control的对象模型。掌握好这些
车型后，他们应该有一个良好的开端。
-
HTH，
Kevin Spencer
Microsoft MVP
..Net开发人员
我宁愿做锤子而不是指甲。
" Frankie" <钽****** @ BeanTown.org>在留言中写道
新闻：％2 *************** @ tk2msftngp13.phx.gbl ...我去过聘请了我的前客户，并在ASP.NET上培训他们的员工
程序员。这些人只有大型机，MS Access，SQL
服务器和VB6桌面应用程序开发经验（绝对没有HTML或Web应用程序经验）。
在跳入任何代码之前我认为让他们了解Web应用程序开发所带来的根本差异和独特挑战是非常重要的（独立于任何特定的应用程序技术; asp，php等） 。
以下是我计划在早期介绍的一些独特挑战（或基本原则）。我很感激您对此列表的反馈 - 请让我知道
您认为应该包含的任何我错过的内容。
1. HTTP（三次握手等）
2.请求/响应模型
3.状态管理
4.客户端逻辑和脚本与服务器端。
5. HTML和CSS（内容和布局vs 。样式）
6.浏览器的变化和限制
谢谢！
-F
< blockquote> Frankie写道：
我被聘请去找我的前客户并在ASP.NET上培训他们的员工
程序员。这些人只有大型机，MS Access，SQL
服务器和VB6桌面应用程序开发经验（绝对没有HTML或Web应用程序经验）。
在跳入任何代码之前我认为让他们了解Web应用程序开发所带来的根本差异和独特挑战是非常重要的（独立于任何特定的应用程序技术; asp，php等） 。
以下是我计划在早期介绍的一些独特挑战（或基本原则）。我很感激您对此列表的反馈 - 请让我知道
您认为应该包含的任何我错过的内容。
1. HTTP（三次握手等）
2.请求/响应模型
3.状态管理
4.客户端逻辑和脚本与服务器端。
5. HTML和CSS（内容和布局vs 。样式）
6.浏览器的变化和限制
谢谢！
-F
制作一定要包含大量的例子，以便（2）Windows Forms
开发人员感到困惑。人们新闻组中的大量例子
在会话结束时试图向客户做事......在我们的商店里，我们有一个人开始了计时器，然后期望能够在计时器事件被触发时更新一些控件...（至少他已经确定了
在组件中找到了计时器而不是来自Windows Forms
标签，所以我给他一些信用）
似乎（对我来说）是人们遇到困难的最大突破
制作。不是说其他人也不是有价值的。
Damien
I have been hired to go to a former client of mine and train their staff
programmers on ASP.NET. These guys have only Mainframe, MS Access, SQL
Server, and VB6 desktop application development experience (with absolutely
no HTML or Web application experience).
Before jumping into any code I think it''s important to get them to
understand the fundamental differences and unique challenges presented by
Web application development (independent of any particular application
technology; asp, php, etc.).
Here are some of the unique challenges (or fundamentals) I plan to cover
early on. I''d appreciate your feedback on this list - please let me know
anything you think should be included that I missed.
1. HTTP (3-way handshake, etc.)
2. The request/response model
3. state management
4. Client-side logic and scripting vs. Server-side.
5. HTML and CSS (content and layout vs. styling)
6. Browser variations and limitations
Thanks!
-F
I think point 3 has to be rammed home good and hard. With emphasis on
connectionless state management techniques. Make it so.
"Frankie" <Ta******@BeanTown.org> wrote in message
news:#X*************@tk2msftngp13.phx.gbl...I have been hired to go to a former client of mine and train their staff
programmers on ASP.NET. These guys have only Mainframe, MS Access, SQL
Server, and VB6 desktop application development experience (with absolutely no HTML or Web application experience).
Before jumping into any code I think it''s important to get them to
understand the fundamental differences and unique challenges presented by
Web application development (independent of any particular application
technology; asp, php, etc.).
Here are some of the unique challenges (or fundamentals) I plan to cover
early on. I''d appreciate your feedback on this list - please let me know
anything you think should be included that I missed.
1. HTTP (3-way handshake, etc.)
2. The request/response model
3. state management
4. Client-side logic and scripting vs. Server-side.
5. HTML and CSS (content and layout vs. styling)
6. Browser variations and limitations
Thanks!
-F
I believe you''ve hit on the "biggies" in the list. In particular, it is
important to explain the stateless nature of the HTTP Request/Response
model, and how the ASP.Net IHttpHandler interface and derived classes (exp.
System.Web.UI.Page) are designed to deal with it. I would also explain fully
the object model for System.Web.UI.Control. With a good grasp of these
models, they should have a good head start.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
I''d rather be a hammer than a nail.
"Frankie" <Ta******@BeanTown.org> wrote in message
news:%2***************@tk2msftngp13.phx.gbl...I have been hired to go to a former client of mine and train their staff
programmers on ASP.NET. These guys have only Mainframe, MS Access, SQL
Server, and VB6 desktop application development experience (with absolutely
no HTML or Web application experience).
Before jumping into any code I think it''s important to get them to
understand the fundamental differences and unique challenges presented by
Web application development (independent of any particular application
technology; asp, php, etc.).
Here are some of the unique challenges (or fundamentals) I plan to cover
early on. I''d appreciate your feedback on this list - please let me know
anything you think should be included that I missed.
1. HTTP (3-way handshake, etc.)
2. The request/response model
3. state management
4. Client-side logic and scripting vs. Server-side.
5. HTML and CSS (content and layout vs. styling)
6. Browser variations and limitations
Thanks!
-F
Frankie wrote:I have been hired to go to a former client of mine and train their staff
programmers on ASP.NET. These guys have only Mainframe, MS Access, SQL
Server, and VB6 desktop application development experience (with absolutely
no HTML or Web application experience).
Before jumping into any code I think it''s important to get them to
understand the fundamental differences and unique challenges presented by
Web application development (independent of any particular application
technology; asp, php, etc.).
Here are some of the unique challenges (or fundamentals) I plan to cover
early on. I''d appreciate your feedback on this list - please let me know
anything you think should be included that I missed.
1. HTTP (3-way handshake, etc.)
2. The request/response model
3. state management
4. Client-side logic and scripting vs. Server-side.
5. HTML and CSS (content and layout vs. styling)
6. Browser variations and limitations
Thanks!
-F
Make sure to include plenty of examples for (2) of where Windows Forms
developers get confused. Plenty of examples in the newsgroups of people
trying to do things to the client when the session times out... Here in
our shop, we had a guy starting a timer, and then expecting to be able
to update some controls when the timer event fired... (At least he''d
found the Timer in the Components rather than from the Windows Forms
tab, so I give him some credit)
It seems (to me) to be the biggest break that people have difficulty
making. Not to say that the others aren''t valuable points too.
Damien
这篇关于为什么Web编程具有挑战性和不同性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
