Reply to thread

Message

<blockquote data-quote="Fast Learner" data-source="post: 422140" data-attributes="member: 649">I don't see the chicken and egg problem the way you do. Yes, we'd have to define some XML DTDs and standard SOAP calls first, but that's an issue no matter what. Once you have a DTD defined for a spell, for example, and a standard call to ask for a spell (name alone should be sufficient for direct access, otherwise something with level or just something generic) then you could ask any spell server in the world for a spell, far into the future. Said spell server could be a local application as well, as towngen is suggesting, so that those who want to sell their applications could provide the same flexibility without having to serve it on the net. The TCP/IP concept is superior to libraries because then they won't have to be compiled/made into any application, but instead can be safely called as new versions of the (serving) application are released. TCP/IP combined with XML and SOAP allow you to write the spec and then add in as many applications as desired at any later time. Since everyone would be using the same basic language for making the requests then it wouldn't matter where the serving application resides, locally or on the net, and it wouldn't matter what OS you were using since the author simply has to know the right calls and use them in his/her code. If at some point in the future you need to update your spec (say, to support something in d20 Modern that's a new concept), the changes needed to each application would be uniform and fairly straightforward, eliminating any limitations or peculiarities of a given OS.It's all about the ubiquity. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" /></blockquote>

[QUOTE="Fast Learner, post: 422140, member: 649"] I don't see the chicken and egg problem the way you do. Yes, we'd have to define some XML DTDs and standard SOAP calls first, but that's an issue no matter what. Once you have a DTD defined for a spell, for example, and a standard call to ask for a spell (name alone should be sufficient for direct access, otherwise something with level or just something generic) then you could ask any spell server in the world for a spell, far into the future. Said spell server could be a local application as well, as towngen is suggesting, so that those who want to sell their applications could provide the same flexibility without having to serve it on the net. The TCP/IP concept is superior to libraries because then they won't have to be compiled/made into any application, but instead can be safely called as new versions of the (serving) application are released. TCP/IP combined with XML and SOAP allow you to write the spec and then add in as many applications as desired at any later time. Since everyone would be using the same basic language for making the requests then it wouldn't matter where the serving application resides, locally or on the net, and it wouldn't matter what OS you were using since the author simply has to know the right calls and use them in his/her code. If at some point in the future you need to update your spec (say, to support something in d20 Modern that's a new concept), the changes needed to each application would be uniform and fairly straightforward, eliminating any limitations or peculiarities of a given OS. It's all about the ubiquity. :) [/QUOTE]

Verification