Posted by Shenzhen Zhengyang Software Conference XLZHU Junior User Points: 0 Posting: 8 From: Registration: 2003-11-02 Posted on 2004-03-19 12:16:05
The following is a personal feeling: March 18th, Go to Zhengyang Software (Shenzhen) Co., Ltd. listened to their product launch. The company launched products is very interesting. The following is an official overview: Appeon for PowerBuilder automatically migrates the PowerBuilder application Go to the web. According to the PowerBuilder application source code, Appeon can completely copy the interface of the client / server application via HTML technology, generating a consistent web application. These APPEON Web applications not only have the availability of client / server models, but also reflect the measurable, effectiveness, security, reliability, and flexibility of multi-layer Web architecture high quality services. The whole process of generating web applications using Appeon for PowerBuilder is done in PowerBuilder IDE, relying on Standard PowerBuilder programming skills, does not require developers to write any HTML, Java, .net, or JavaScript code. Enterprises can develop client / server applications with PowerBuilder, then use the Appeon for PowerBuilder to publish PB programs, which can generate web applications. Enterprises can also convert existing client / server applications to web applications. Because there is an Appeon for PowerBuilder, developing a troubles such as a web application is also familiar and simple, just developing PowerBuilder applications or optimization existing applications.
If you have developed an application before using PB, you must know this software. My question is as follows:
What is the conversion performance? What way is you run on a web server? What is the requirements for the web server?
How to solve the configuration of application and network, data connection, etc. How to solve the concurrency in multiple user status?
How to ensure data encryption and security? Do you support hardware level identification (such as dongle)?
Do you support direct modifications of the web layer? What is the form of the final file after conversion?
Through the introduction at the press (the engineer has a .NET one through, it is very unhappy), after the technical personnel exchange and its own trial, some personal opinions can be divided into two aspects: technology and market:
Technical aspects:
1. Support from the migration of C / S applications from PB, VB, DEPHI to B / S applications (current product only supports PB), can attract PB programmers to upgrade C / S applications and develop new applications in PB environments
2. The development environment of PB is integrated, and it is very fast and convenient to the web after the conversion is successful, inheriting the advantages of 4GL.
3. Follow the Web to restore the PB's UI interface, and use the household operation very familiar and convenient.
4. Work with Sybase to develop EJB containers on Easerver, the development direction is J2EE, there will be better transplantability
insufficient:
1. The release method is to pack PB applications into one component on an application server, and developers cannot know the conversion mode, causing flexible and scalability. Just like the PFC in the PB, it will be a bundle.
2. Do not support a separate revision of the web layer, you need to modify it in PB, this is very fatal, if you have deployed to the production environment ...? #!
2. The development environment is still using PB, and there is no solution to the PB's inherent shortcomings: such as the reflection of OO characteristics such as team development, layering, inheritance, design mode. The most due to the scalability, it is estimated that the senior PB programmer has this Experience: Application can only be planted on the PB and cannot do other extensions.
3. The current product only supports a version of PB8.0. It does not support the previous 6.5, 7.0, no support now 9.0, 10.0, if not 8.0, you need to upgrade or downgrade your development tool, huh, a small expenditure ... (8.0 does not support .NET) 4. Application server, subject to the protocol limit, only Sybase's Easerver and Adaptive Server Anywhere. Attention, can't change it.
5. Support for custom class libraries, hardware encryption, and .NET's Web Service components, it is still assessed (just studying documents, the current version does not support .NET)
6. The performance and load balancing of the conversion still have to be evaluated
7.4GL and MIS development is getting more and more, must attract enough other development groups (VB, DEPHI) to survive
Market:
1. Combine with Sybase is very close, support for future support from development tools to background databases and application servers
2. The product is in the initial stage, and the support for users is very strong.
Disadvantages:
1. Too much tight with Sybase. To know that the EJB server market is full of fire, if the Easerver exits the market, it is not good.
2. PB's strength in the MIS field, the ultimate users developed products are also small and medium-sized enterprises. The platform is also Windows, how to persuade them to pay Easerver, especially after IIS, after IIS?
3. The corporate market is the focus of Java and .NET competition, how to strengthen the PB again or not to get rid of MIS limitations, software companies want to enter the corporate market, are only afraid to abandon PB?
Overall, if the software company has a product developed by PB8, you can evaluate this product first, it is definitely no harm to yourself, but the development group of PB only accounts for 4.9% in China. If there is no strong function to attract enough Many development groups use this technology, just afraid that the road will be difficult to go ...
