Re: extensible ozone API

• To: thomas.strauss@philips.com, <ozone-users@ozone-db.org>
• Subject: Re: extensible ozone API
• From: Falko Braeutigam <falko@softwarebuero.de>
• Date: Mon, 23 Oct 2000 12:01:13 +0200
• Delivered-To: softw7-ozone-db:org-ozone-users@ozone-db.org
• In-Reply-To: <0056900013120730000002L002*@MHS>
• Organization: SMB
• References: <0056900013120730000002L002*@MHS>

On Mon, 23 Oct 2000, thomas.strauss@philips.com wrote:
> ---------------------- Forwarded by Thomas Strauss/HBG/MS/PHILIPS on 23.10.2000 09:51 ---------------------------
> 
> 
> thomas.strauss@germanynet.de on 22.10.2000 21:08:50
> To:	Thomas Strauss/HBG/MS/PHILIPS@EMEA1
> cc:	 
> Subject:	Re: extensible ozone API
> Classification:	
> 
> Hi
> 
> I thing for the described situation something like a virtual constructor
> would be a good situation. The context for the usage is known and therefor
> the type is known in advance.
What is a "virtual constructor"? How would the client code look like using such
a thing?

> 
> Maybe the type information could be transfered with an tagging interface.
Can you explain more?


Falko
-- 
______________________________________________________________________
Falko Braeutigam                              mailto:falko@smb-tec.com
SMB GmbH                                        http://www.smb-tec.com

• References:
  • Re: extensible ozone API
    • From: thomas.strauss@philips.com

• Prev by Date: Re: XML document too large for storing ?
• Next by Date: Re: XML documents too large?
• Prev by thread: Re: extensible ozone API
• Next by thread: extensible ozone API
• Index(es):
  • Date
  • Thread