xml/rss

[f3l1x]

Does dplogin have xml or rss export? I will need it in my new project ..


Players/clans exporting to xml for exam.:

Code: [Select]

<?xml version="1.0" encoding="UTF-8"?>
<players>
<player>
<name>Felix</name>
<start>DATE</start>
<nicks>F3L1X,Giro,etc..</nicks>
                <activeClanTag> [eX] </activeClanTag>
        ....
</player>
</players>

or rss could be also good... I think that's not a big problem and it's helpful stuff..

[webhead]

wouldn't that be nice.

[jitspoe]

http://dplogin.com/dplogin/featurevote/feature.php?id=10238

[f3l1x]

Any news in this case? If you dont have much time, I could help to you. I have experiences with it.

[payl]

Isn't RSS format for NEWS?

[XtremeBain]

Or podcasts? Or you could use RSS for new maps/textures/builds/players.

He (and other folks) want an XML API so that you could do lookups to a dplogin web service. It doesn't matter if the request/response format is XML, JSON or even like an INI. It's a little silly to download 5KB of HTML to extract 200 bytes of player information.

If I were to try and dump all of the player info, I'd hammer the display player page with Perl's HTML::TableExtract module to rip out the player data you want.

[f3l1x]

I think that websites needs to remake/redesign to new technology/style. Dplogin is maybe adequate to minimum requirements but everythink needs to evolve.

[payl]

Code: [Select]

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
 <channel>
  <title>Wiadomości</title>
  <link>http://przykladowy_adres.pl/</link>
  <description>Informacje o nowościach naszej firmy</description>
   <item>
     <title>Nowa myszka w sprzedaży!</title>
     <pubDate>2007-08-08 20:39:21</pubDate>
     <link>http://przykladowy_adres.pl/rss/info001.html</link>
     <description>Nowa myszka optyczna firmy Mouse Ltd. wchodzi na rynek.
     W ramach promocji przewidziana jest bardzo atrakcyjna cena.</description>
     <enclosure url="http://przykladowy_adres.pl/nazwa_pliku.mp3" size="rozmiar_w_bajtach" type="audio/mpeg"/>
   </item>
 </channel>
</rss>
That is RSS, it bases on XML, but it have ONLY fields like title,channel,item,rss etc. So creating it is NONSENS.

Or you could use RSS for new maps/textures/builds/players.

Wrong, its only for news. For other things with tree of items with values is XML (and RSS bases on it). And without tree, just section and field is INI. But RSS cannot be used like this, because it's impossible to create it with RSS specification, and if it's not OK with RSS specification, then its XML. So: RSS CANNOT BE USED AS INFORMATION HOLDER (even if you want to lose ur time to do that, this is still nonsens).

[webhead]

I think he meant it could be used for *news* about new maps/textures/build/players.

[f3l1x]

What means exactly RSS for you payl?

[payl]

I think he meant it could be used for *news* about new maps/textures/build/players.

Oh ... =]

What means exactly RSS for you payl?

This is news publishing standard, in which .RSS file is used (and it bases on XML). Why you ask?

[f3l1x]

Just for info.. Im webdevoleper, so that.

[ViciouZ]

JSON would also be good. It's also ridiculously simple to implement in PHP, after all the MySQL stuff is done, this is usually enough:

Code: [Select]

$row = mysql_fetch_assoc($result);
$json = json_encode($row);
header("Content-Type: text/plain");
echo $json;


[f3l1x]

Yep. If would be this site more open for help, we can make RSS/XML ouputs ;-)