4. Expose the methods. Once the application has been imported into the framework
and the appropriate con?¬? guration applied, the framework must be told which
areas of the application should be made public. This step has the greatest
potential to threaten the security of the application. Often the easiest approach
to this step is for a developer is simply to mark all methods as public to
guarantee that the application will function correctly. This can lead to a number
of issues, with areas of the application that should remain private being
exposed to a user. This step should take the bulk of a developer??™s time during
a Web 2.0 migration to ensure that he or she knows exactly what sections of the
application will be exposed to users.
5. Run the framework. Finally, when the framework is fully imported and con?¬? gured,
the framework is run and generates the new Web 2.0??“style application. Depending
on the framework, the output can vary signi?¬? cantly. For example, with Microsoft
ASP.NET AJAX, the output will be like a normal web application. On the other
hand, the output of a Java application run through the Google Web Toolkit
framework will be JavaScript and HTML ?¬? les that can then be served from any
static web server.
Pages:
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347