Support servers like Tomcat, Resin, WebSphere, WebLogic etc.
Multi-languages(English/Chinese...)
Support RSS 2.0
RSS syndication
Unlimited XML news source
Customizable fetch time interval
Customizable max entry count
Customizable max content size
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>會員登錄</TITLE>
<META http-equiv=Content-Type content="text/html charset=gb2312">
<SCRIPT language=javascript id=clientEventHandlersJS>
This script was designed as a stand alone script which can be easily intergrate into any existing website as it is,but if you want to intergrate it into a site which uses a content management format, then some alterations will have to be done for
it to work properly. Remember this is a project and I am constantly working to improve it, so I can t guarantee that
it will work for everyones needs, but dammmmd close.
Get up and running with PHP 5, Apache, and MySQL with ease. This guide demonstrates how to display dynamic content, build your own contact management system, create custom reports, work with XML, and much more
SDP, Service Delivery Platform, is more for telecom operators who want to manage the Data Service better delivered to the end device users by bridging with back-end content providers. Operators rely on the content provider to create & distribute data content to different types of devices. This is different from the open world in the internet communication. Operators must control who can access what content based on his rate plans. Also, based the content access results, the process will be recorded as the transaction records based on which billing statements can be generated to collected the money and shared by operators and content providers. I am working on the conceptual architecture level and the real implementation is very complicated due to too many types of service from different content providers to different types of devices based on the different types of the rate plans.
SDP, Service Delivery Platform, is more for telecom operators who want to manage the Data Service better delivered to the end device users by bridging with back-end content providers. Operators rely on the content provider to create & distribute data content to different types of devices. This is different from the open world in the internet communication. Operators must control who can access what content based on his rate plans. Also, based the content access results, the process will be recorded as the transaction records based on which billing statements can be generated to collected the money and shared by operators and content providers. I am working on the conceptual architecture level and the real implementation is very complicated due to too many types of service from different content providers to different types of devices based on the different types of the rate plans.
本文從英文C–FAQ (2004 年7 月3 日修訂版) 翻譯而來。本文的中文版權(quán)為
朱群英和孫云所有。本文的內(nèi)容可以自由用于個人目的，但是不可以未經(jīng)許可出
版發(fā)行。英文版權(quán)為Steve Summit 所有，詳情見下面的英文版權(quán)說明。
The English version of this FAQ list is Copyright 1990-2004 by Steve Summit.
Content from the book 《C Programming FAQs: Frequently Asked Questions》is
made available here by permission of the author and the publisher as a service to
the community. It is intended to complement the use of the published text and is
protected by international copyright laws. The on-line content may be accessed
freely for personal use but may not be republished without permission.
