| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | XML |
JV> Nor will it get to the top for integration in that week's and JV> who knows how mainy next weeks' nodelists. And that is a loss, not JV> for me, but for the net, because it spells loss of connectivity for JV> that or those unlisted or wrongly listed node AND all other correct JV> changes that were in that same list. Until I find out when coming JV> home from a holyday or the hospital. JV> Capice now? No. You have the exact same problem today. But in my example it would only affect the node who sent the faulty data, not the whole nodelist. JV> Then do so and have it tested. As soon as there is a spec, I will be among the first to implement it at my system. Fact is, I'm allready using XML internaly with very good results. //Micke ---* Origin: OX12.NET (2:204/710) SEEN-BY: 633/267 270 @PATH: 204/710 20/11 2411/413 2432/200 774/605 123/500 106/1 379/1 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.