Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
How to pass views with COM?
Message
From
20/12/1999 01:25:08
 
 
To
19/12/1999 12:53:22
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Miscellaneous
Thread ID:
00304428
Message ID:
00305997
Views:
31
In reference to the parallel discussion here on stateless objects, XML is the next logical choice for stateless messaging. There is a practical limit to the number of parameters that you can pass in a single method call before handling your object becomes ugly. (Code Complete states that any routine receiving more than seven parameters should be redesigned). The problem is, with stateless programming, you can't rely on object properties, so there needs to be another way. The answer to this is XML. With XML, you can build a structured request document that contains all of the needed parameters for the method in a single string. You then pass this string as a single parameter to your object, which knows how to parse it and get its operating instructions.

For anybody who hasn't seen it, BizTalk is an application framework that requires that you build a BizTalk compatible Schema for each of your businees messages (the schema standard is not complex, and building a valid BizTalk schema is not difficult). Once you have done this, your application speaks 'BizTalk', and all messaging to and from your application is accomplished with XML documents validated by your custom Schema.


Hell Eric, anyone can create their own parameter string schema and parser. For example, my of my framework classes accept an array in the Init and, if evaluated as an array, is parsed to set (or add) properties.

Incorporating BizTalk server in the picture (optional with the framework) allows asynchronous application messaging (using MSMQ) facilitated by content routed messages. IOW, My application A on machine X invokes action on application B on machine Y by building an XML message and throwing it at the BizTalk server, which handles routing. THe name and location of the remote server are built into the message, and read by the BizTalk server, and ultimately by the object itself. This is like the results of DCOM, but without the overhead and complexity of a connection. A standard like BizTalk is an idea whose time has come. This is going to be exciting to watch and take part in.

Now that is the real benefit to BizTalk.

I have no idea if BizTalk will win this standards war, but I have a feeling it will. Somebody has to, and this framework is much further along than any other I've seen, and MS surely has the muscle to push it. Keep an eye on this one- it's gonna get good.

I certainly hope so. There is too much technology in flux at the present.
- Jeff
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform