Software in client-server architecture with one fat-client
The way to use the SDK in this architecture is basically the same as in a standard Windows application, that is, Managed mode).
An example of this architecture is an ASP.NET or J2EE application, but with only one workplace to edit and produce cards. In respect of the SDK usage, the term fat-client indicates the usage of the CardDesigner for card type administration and storing its card type definitions locally. The advantage of this solution is a quick and easy integration as the CardDesigner supports all functionality for card type administration.
Administration of cards, capture image and produce cards
The way to use the SDK in this architecture is basically the same as in a standard Windows application. But unlike the full client-server architecture, there is only one workstation using the CardDesigner and the production component. Both components use the layouts and encoding rules which are stored locally on this workstation in the same way as with the standard Windows application.
Image data, like photos and signatures, are also captured using the capture component. The resulting images are typically stored in your server's database.
Examples
The SDK provides an HTML example which demonstrates this architecture in combination with JavaScript: The HTML, sent from a Web server1 is running in the browser and accesses local card types managed by the Card Designer. Note that the demonstration of this mode requires to check the Managed Mode check box, as set by default.
The link to this example is located in the folder with the corresponding name in the examples directory of the SDK installation. Or you can enter the URL http://localhost:54880/components.htm into your browser which opens the sample HTML page.
1 The IDProductionService is the SDK's SOAP and RESTful web service, but also acts as simple local application web server. It hosts a service user interface, also containing the components page for demonstration purposes. In a real world application, such an HTML will come from your, typically J2EE or ASP .NET, application web server.