Reply to thread

Message

<blockquote data-quote="Davin" data-source="post: 417486" data-attributes="member: 1183">Good ideaA good idea, but difficult to develop on a wide scope.&nbsp; (For one thing, it's hard to get a lot of people to agree on a standard.&nbsp; For another, you're talking about a ton of definitions to deal with and it'll take quite some time just to come up with it.)&nbsp; I think organization and standardization (as in preparing for connections) is going to be a lot tougher than the pure communication part of the project.TCP/IP sounds like a good idea if complete interoperability is needed.&nbsp; Coding for TCP/IP communication is easy enough, but there are still technical issues to overcome.&nbsp; For instance, only one program can listen on a given port at once.&nbsp; However, if you restrict yourself a little you have other options.&nbsp; For instance, if your application runs on a Mac (for one example), then its reasonable to assume that any local applications are also Mac applications and you can use any Mac-specific intra-machine communications facilities to best advantage.&nbsp; (But that does keep you from talking to another kind of machine.)&nbsp; For another example, if you're running under Windows you can work with DLL interfaces (or SO interfaces under Linux), giving you an advantage in several functional areas.You've also got issues about automatically starting up non-specific programs.&nbsp; There's lots to worry about there.As far as I've been able to tell from my brief contacts there, the D20-XML Yahoo group is concentrating solely on a *character* definition.&nbsp; Thus, anything for exchanging other kinds of data isn't in their purvue and will need to be developed separately.Klintus Fang - You needed worry about port security as all the communication would be behind your firewall within your own machine (unless you choose differently).Don't forget that XML, while regular, isn't trivial to parse.&nbsp; Some OS's may or may not have software assistance for that, assuming that they've even got the software up to date for it.&nbsp; Don't assume that anyone (either from the coder's standpoint or the user's) can handle XML input trivially.</blockquote>

[QUOTE="Davin, post: 417486, member: 1183"] [b]Good idea[/b] A good idea, but difficult to develop on a wide scope. (For one thing, it's hard to get a lot of people to agree on a standard. For another, you're talking about a ton of definitions to deal with and it'll take quite some time just to come up with it.) I think organization and standardization (as in preparing for connections) is going to be a lot tougher than the pure communication part of the project. TCP/IP sounds like a good idea if complete interoperability is needed. Coding for TCP/IP communication is easy enough, but there are still technical issues to overcome. For instance, only one program can listen on a given port at once. However, if you restrict yourself a little you have other options. For instance, if your application runs on a Mac (for one example), then its reasonable to assume that any local applications are also Mac applications and you can use any Mac-specific intra-machine communications facilities to best advantage. (But that does keep you from talking to another kind of machine.) For another example, if you're running under Windows you can work with DLL interfaces (or SO interfaces under Linux), giving you an advantage in several functional areas. You've also got issues about automatically starting up non-specific programs. There's lots to worry about there. As far as I've been able to tell from my brief contacts there, the D20-XML Yahoo group is concentrating solely on a *character* definition. Thus, anything for exchanging other kinds of data isn't in their purvue and will need to be developed separately. Klintus Fang - You needed worry about port security as all the communication would be behind your firewall within your own machine (unless you choose differently). Don't forget that XML, while regular, isn't trivial to parse. Some OS's may or may not have software assistance for that, assuming that they've even got the software up to date for it. Don't assume that anyone (either from the coder's standpoint or the user's) can handle XML input trivially. [/QUOTE]

Verification