<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/tag/server">
<title>Public marks with tag server</title>
<description>Public marks with tag server</description>
<link>http://blogmarks.net/marks/tag/server</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/vrossign/mark/1058565466"/>
<rdf:li resource="http://blogmarks.net/api/user/RETFU/mark/1058551154"/>
<rdf:li resource="http://blogmarks.net/api/user/danijelzi/mark/1058549169"/>
<rdf:li resource="http://blogmarks.net/api/user/danijelzi/mark/1058542686"/>
<rdf:li resource="http://blogmarks.net/api/user/danijelzi/mark/1058522669"/>
<rdf:li resource="http://blogmarks.net/api/user/vrossign/mark/1058519939"/>
<rdf:li resource="http://blogmarks.net/api/user/talou/mark/1058508826"/>
<rdf:li resource="http://blogmarks.net/api/user/talou/mark/1058508708"/>
<rdf:li resource="http://blogmarks.net/api/user/talou/mark/1058508707"/>
<rdf:li resource="http://blogmarks.net/api/user/talou/mark/1058508705"/>
<rdf:li resource="http://blogmarks.net/api/user/newandforever/mark/1058506556"/>
<rdf:li resource="http://blogmarks.net/api/user/greut/mark/1058499632"/>
<rdf:li resource="http://blogmarks.net/api/user/Tiagut/mark/1058485281"/>
<rdf:li resource="http://blogmarks.net/api/user/danijelzi/mark/1058472999"/>
<rdf:li resource="http://blogmarks.net/api/user/Adri1bip/mark/1058463803"/>
<rdf:li resource="http://blogmarks.net/api/user/costel/mark/1058456631"/>
<rdf:li resource="http://blogmarks.net/api/user/Xavier Lacot/mark/1058440964"/>
<rdf:li resource="http://blogmarks.net/api/user/br1o/mark/1058556668"/>
<rdf:li resource="http://blogmarks.net/api/user/newandforever/mark/1058398590"/>
<rdf:li resource="http://blogmarks.net/api/user/delavigne/mark/1058383789"/>
<rdf:li resource="http://blogmarks.net/api/user/br1o/mark/1058556780"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058379897"/>
<rdf:li resource="http://blogmarks.net/api/user/eaque/mark/1058368838"/>
<rdf:li resource="http://blogmarks.net/api/user/Giraultises/mark/1058357010"/>
<rdf:li resource="http://blogmarks.net/api/user/RETFU/mark/1058356765"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/vrossign/mark/1058565466">
<title>After the Deadline</title>
<link>http://open.afterthedeadline.com/</link>
<description></description>
<dc:date>2009-10-28T10:47:59Z</dc:date>
<dc:author>vrossign</dc:author>
<dc:subject>language, spell, check, checking, spell checking, java, server, atester</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://open.afterthedeadline.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/28/e5b2773c307028860df8a5b35dc2f02f.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://open.afterthedeadline.com/">After the Deadline</a></h4>
 
by <a href="http://blogmarks.net/user/vrossign">vrossign</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/language">language</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/spell">spell</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/check">check</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/checking">checking</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/spell%2Bchecking">spell checking</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/java">java</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/atester">atester</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058565466">Copy</a> | 
<a href="http://blogmarks.net/link/3395292">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/RETFU/mark/1058551154">
<title>Mammoth Server</title>
<link>http://mammothserver.org/</link>
<description></description>
<dc:date>2009-10-15T17:23:04Z</dc:date>
<dc:author>RETFU</dc:author>
<dc:subject>server, streaming, socket</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://mammothserver.org/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/15/4f3aa3141737f676371abd3daeeedf4c.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://mammothserver.org/">Mammoth Server</a></h4>
 
by <a href="http://blogmarks.net/user/RETFU">RETFU</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/streaming">streaming</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/socket">socket</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058551154">Copy</a> | 
<a href="http://blogmarks.net/link/3384389">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/danijelzi/mark/1058549169">
<title>Dell PowerEdge R210 Server</title>
<link>http://getitequipped.com/dell-poweredge-r210-rack-server.html</link>
<description>The Dell PowerEdge R210 is an entry-level rack server, featuring a compact 15.5 inches deep 1U chassis and a single CPU socket.

Designed for small businesses and larger offices, the Intel 3420 chipset-based PowerEdge R210 is offered with one of Intel Xeon 3400 Series quad-core processors, up to 16GB of unbuffered DDR3 memory using 4 DIMM slots, and up to two 2.5”/ 3.5” SAS, SATA or SSD non hot-plug drives.</description>
<dc:date>2009-10-13T13:21:00Z</dc:date>
<dc:author>danijelzi</dc:author>
<dc:subject>dell, poweredge, server, r210, rack, business server</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://getitequipped.com/dell-poweredge-r210-rack-server.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/13/d605dde6a63d1a7285da4c16386c120d.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://getitequipped.com/dell-poweredge-r210-rack-server.html">Dell PowerEdge R210 Server</a></h4>
 
by <a href="http://blogmarks.net/user/danijelzi">danijelzi</a> 
<p class="description">The Dell PowerEdge R210 is an entry-level rack server, featuring a compact 15.5 inches deep 1U chassis and a single CPU socket.

Designed for small businesses and larger offices, the Intel 3420 chipset-based PowerEdge R210 is offered with one of Intel Xeon 3400 Series quad-core processors, up to 16GB of unbuffered DDR3 memory using 4 DIMM slots, and up to two 2.5”/ 3.5” SAS, SATA or SSD non hot-plug drives.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dell">dell</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/poweredge">poweredge</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/r210">r210</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rack">rack</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/business%2Bserver">business server</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058549169">Copy</a> | 
<a href="http://blogmarks.net/link/3382718">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/danijelzi/mark/1058542686">
<title>Dell PowerEdge T310 Server Overview</title>
<link>http://getitequipped.com/dell-poweredge-t310.html</link>
<description>The Dell PowerEdge T310 is the company’s latest single-socket tower server.

Along with a single Intel Xeon 3400 Series quad-core CPU, the Intel 3420 chipset-based PowerEdge T310 includes up to 32GB of registered (RDIMM) or up to 8GB of unregistered (UDIMM) DDR3 memory, and up to four 3.5″ cabled or hot-swap SAS or SATA hard drives for a maximum of 4TB of internal storage.

The system has an onboard SATA controller without RAID functionality, but there’s a variety of additional storage controllers supporting up to RAID 10. The basic network adapter is an embedded dual Gigabit NIC, which can be accompanied by various single-, dual-, or quad- port Gigabit cards. For server management, customers can use the baseboard management controller and one of optional iDRAC6 controllers.

Dell’s T310 features the Matrox G200eW GPU, a DVD drive, optional PowerVault tape or hard drives for backups, and five PCIe Gen. 2 slots: two x8 slots (one with x16 connector), a x4 slot (with x8 connector), and two x1 slots.

Power supply options include a redundant 400W and a non-redundant 375W unit.

On the front of the chassis, the 20.5 inches deep tower server has an optional LCD screen for system monitoring.

The new PowerEdge comes without operating system or with one of Windows Server, Windows Essential Business Server, and Small Business Server editions, as well as with optional Novell SUSE Linux Enterprise Server or Red Hat Enterprise Linux.

The starting price for the Dell PowerEdge T310 is $949, with the 3Yr Basic Hardware Warranty included.

The server can be purchased at dell.com.</description>
<dc:date>2009-10-08T16:03:52Z</dc:date>
<dc:author>danijelzi</dc:author>
<dc:subject>dell, poweredge, T310, server, intel, Xeon, single socket, tower</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://getitequipped.com/dell-poweredge-t310.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/08/b1ce28b52b1b8d847c2d2cfabf7f5256.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://getitequipped.com/dell-poweredge-t310.html">Dell PowerEdge T310 Server Overview</a></h4>
 
by <a href="http://blogmarks.net/user/danijelzi">danijelzi</a> 
<p class="description">The Dell PowerEdge T310 is the company’s latest single-socket tower server.

Along with a single Intel Xeon 3400 Series quad-core CPU, the Intel 3420 chipset-based PowerEdge T310 includes up to 32GB of registered (RDIMM) or up to 8GB of unregistered (UDIMM) DDR3 memory, and up to four 3.5″ cabled or hot-swap SAS or SATA hard drives for a maximum of 4TB of internal storage.

The system has an onboard SATA controller without RAID functionality, but there’s a variety of additional storage controllers supporting up to RAID 10. The basic network adapter is an embedded dual Gigabit NIC, which can be accompanied by various single-, dual-, or quad- port Gigabit cards. For server management, customers can use the baseboard management controller and one of optional iDRAC6 controllers.

Dell’s T310 features the Matrox G200eW GPU, a DVD drive, optional PowerVault tape or hard drives for backups, and five PCIe Gen. 2 slots: two x8 slots (one with x16 connector), a x4 slot (with x8 connector), and two x1 slots.

Power supply options include a redundant 400W and a non-redundant 375W unit.

On the front of the chassis, the 20.5 inches deep tower server has an optional LCD screen for system monitoring.

The new PowerEdge comes without operating system or with one of Windows Server, Windows Essential Business Server, and Small Business Server editions, as well as with optional Novell SUSE Linux Enterprise Server or Red Hat Enterprise Linux.

The starting price for the Dell PowerEdge T310 is $949, with the 3Yr Basic Hardware Warranty included.

The server can be purchased at dell.com.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dell">dell</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/poweredge">poweredge</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/T310">T310</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/intel">intel</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Xeon">Xeon</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/single%2Bsocket">single socket</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tower">tower</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058542686">Copy</a> | 
<a href="http://blogmarks.net/link/3377294">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/danijelzi/mark/1058522669">
<title>Dell PowerEdge T710 Tower Server Overview</title>
<link>http://getitequipped.com/dell-poweredge-t710.html</link>
<description>The Dell PowerEdge T710 is the company’s new dual-socket tower server.

The virtualization oriented T710 is based on the Intel 5520 chipset and supports up to two quad-core or dual-core Intel Xeon 5500 series processors. It has 18 DIMM slots for up to 144GB of ECC DDR3 memory and supports 16 2.5-inch or 8 3.5-inch hot-plug hard drives, depending on customer’s choice. The 5U chassis, mountable in 19″ racks, also includes two media bays for optical drives or tape backup units, and two power supplies with optional redundancy.

Integrated storage controller choices include SAS 6/iR or PERC 6/i SAS RAID, but there’s also a variety of additional HDD controllers. Customers can also choose between various host bus controller, management card, and network adapter options.

Dell’s T710 has 6 PCI Express 2.0 slots and the integrated Matrox G200 video chip, and offers an interactive LCD on the front of the server for system health monitoring, alerts and control of basic management configuration.

Regarding software, the PowerEdge T710 ships without OS or with one of Windows Sever, SUSE Linux, or Red Hat Linux editions, with VMware or Citrix virtualization software, and with various optional management and backup applications.

The Dell PowerEdge T710 currently starts at $1,199 at the official Dell Small Business website.</description>
<dc:date>2009-09-28T21:45:25Z</dc:date>
<dc:author>danijelzi</dc:author>
<dc:subject>dell, poweredge, t710, server, tower, dual-socket, Quad-Core, dual-core, storage, integrated</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://getitequipped.com/dell-poweredge-t710.html"><img border="0" src="http://blogmarks.net/screenshots/2009/09/28/0d48f6f26e2a481389a605462c5c8990.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://getitequipped.com/dell-poweredge-t710.html">Dell PowerEdge T710 Tower Server Overview</a></h4>
 
by <a href="http://blogmarks.net/user/danijelzi">danijelzi</a> 
<p class="description">The Dell PowerEdge T710 is the company’s new dual-socket tower server.

The virtualization oriented T710 is based on the Intel 5520 chipset and supports up to two quad-core or dual-core Intel Xeon 5500 series processors. It has 18 DIMM slots for up to 144GB of ECC DDR3 memory and supports 16 2.5-inch or 8 3.5-inch hot-plug hard drives, depending on customer’s choice. The 5U chassis, mountable in 19″ racks, also includes two media bays for optical drives or tape backup units, and two power supplies with optional redundancy.

Integrated storage controller choices include SAS 6/iR or PERC 6/i SAS RAID, but there’s also a variety of additional HDD controllers. Customers can also choose between various host bus controller, management card, and network adapter options.

Dell’s T710 has 6 PCI Express 2.0 slots and the integrated Matrox G200 video chip, and offers an interactive LCD on the front of the server for system health monitoring, alerts and control of basic management configuration.

Regarding software, the PowerEdge T710 ships without OS or with one of Windows Sever, SUSE Linux, or Red Hat Linux editions, with VMware or Citrix virtualization software, and with various optional management and backup applications.

The Dell PowerEdge T710 currently starts at $1,199 at the official Dell Small Business website.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dell">dell</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/poweredge">poweredge</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/t710">t710</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tower">tower</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dual-socket">dual-socket</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Quad-Core">Quad-Core</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dual-core">dual-core</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/storage">storage</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/integrated">integrated</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058522669">Copy</a> | 
<a href="http://blogmarks.net/link/3358717">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/vrossign/mark/1058519939">
<title>SVN Server Admin Issue: Fix It! « Smashing Magazine</title>
<link>http://www.smashingmagazine.com/2009/09/25/svn-strikes-back-a-serious-vulnerability-found/</link>
<description></description>
<dc:date>2009-09-25T12:44:57Z</dc:date>
<dc:author>vrossign</dc:author>
<dc:subject>svn, admin, server, alire</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.smashingmagazine.com/2009/09/25/svn-strikes-back-a-serious-vulnerability-found/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/25/304bd914afce86143635fdcab550f019.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.smashingmagazine.com/2009/09/25/svn-strikes-back-a-serious-vulnerability-found/">SVN Server Admin Issue: Fix It! « Smashing Magazine</a></h4>
 
by <a href="http://blogmarks.net/user/vrossign">vrossign</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/svn">svn</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/admin">admin</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/alire">alire</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058519939">Copy</a> | 
<a href="http://blogmarks.net/link/3356477">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/talou/mark/1058508826">
<title>PyGo Wave Server is here - play with the Waves NOW! — Wavety.com</title>
<link>http://wavety.com/pygo-wave-server/</link>
<description></description>
<dc:date>2009-09-18T17:21:45Z</dc:date>
<dc:author>talou</dc:author>
<dc:subject>server, wave</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://wavety.com/pygo-wave-server/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/18/383b6701d8c3a22fed5dbf89d6011df7.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://wavety.com/pygo-wave-server/">PyGo Wave Server is here - play with the Waves NOW! — Wavety.com</a></h4>
 
by <a href="http://blogmarks.net/user/talou">talou</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wave">wave</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058508826">Copy</a> | 
<a href="http://blogmarks.net/link/3346895">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/talou/mark/1058508708">
<title>Google Wave Federation Protocol with Prosody XMPP server - Bloggitation</title>
<link>http://zhekov.freehostia.com/blog/2009/07/30/google-wave-prosody-xmpp-server/</link>
<description></description>
<dc:date>2009-09-18T14:36:28Z</dc:date>
<dc:author>talou</dc:author>
<dc:subject>google, xmpp, server, wave</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://zhekov.freehostia.com/blog/2009/07/30/google-wave-prosody-xmpp-server/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/18/4fc4d32485a972c72f3064fd21ac8128.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://zhekov.freehostia.com/blog/2009/07/30/google-wave-prosody-xmpp-server/">Google Wave Federation Protocol with Prosody XMPP server - Bloggitation</a></h4>
 
by <a href="http://blogmarks.net/user/talou">talou</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xmpp">xmpp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wave">wave</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058508708">Copy</a> | 
<a href="http://blogmarks.net/link/3346810">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/talou/mark/1058508707">
<title>Prosody Installation For the Impatient | DotProfile Consulting</title>
<link>http://www.dotprofileconsulting.com/node/4</link>
<description></description>
<dc:date>2009-09-18T14:35:54Z</dc:date>
<dc:author>talou</dc:author>
<dc:subject>im, jabber, xmpp, server</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.dotprofileconsulting.com/node/4"><img border="0" src="http://blogmarks.net/screenshots/2009/09/18/afa77f64d248173e69da1ba2e2add83e.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.dotprofileconsulting.com/node/4">Prosody Installation For the Impatient | DotProfile Consulting</a></h4>
 
by <a href="http://blogmarks.net/user/talou">talou</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/im">im</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/jabber">jabber</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xmpp">xmpp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058508707">Copy</a> | 
<a href="http://blogmarks.net/link/3346809">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/talou/mark/1058508705">
<title>Prosody IM</title>
<link>http://prosody.im/</link>
<description></description>
<dc:date>2009-09-18T14:34:32Z</dc:date>
<dc:author>talou</dc:author>
<dc:subject>im, jabber, xmpp, server</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://prosody.im/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/18/f0cda300ffb430dc7a6adc9c34a378ae.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://prosody.im/">Prosody IM</a></h4>
 
by <a href="http://blogmarks.net/user/talou">talou</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/im">im</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/jabber">jabber</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xmpp">xmpp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058508705">Copy</a> | 
<a href="http://blogmarks.net/link/3346807">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/newandforever/mark/1058506556">
<title>ламинатор</title>
<link>http://ava.com.ua/category/20/212/</link>
<description>ламинатор</description>
<dc:date>2009-09-19T11:03:19Z</dc:date>
<dc:author>newandforever</dc:author>
<dc:subject>server, dvd, web, dabogovo, bookmarks, ламинатор</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://ava.com.ua/category/20/212/"><img border="0" src="http://blogmarks.net/screenshots/2007/11/18/706a1e12fcdbccd11c7efc1741e4fde5.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://ava.com.ua/category/20/212/">ламинатор</a></h4>
 
by <a href="http://blogmarks.net/user/newandforever">newandforever</a> 
<p class="description">ламинатор</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dvd">dvd</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dabogovo">dabogovo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bookmarks">bookmarks</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/%25D0%25BB%25D0%25B0%25D0%25BC%25D0%25B8%25D0%25BD%25D0%25B0%25D1%2582%25D0%25BE%25D1%2580">ламинатор</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058506556">Copy</a> | 
<a href="http://blogmarks.net/link/2545513">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/greut/mark/1058499632">
<title>Tornado Web Server Documentation</title>
<link>http://www.tornadoweb.org/documentation#wsgi-and-google-appengine</link>
<description>&lt;blockquote&gt;&lt;p&gt;Tornado comes with limited support for WSGI. However, since WSGI does not support non-blocking requests, you cannot use any of the asynchronous/non-blocking features of Tornado in your application if you choose to use WSGI instead of Tornado's HTTP server. Some of the features that are not available in WSGI applications: @tornado.web.asynchronous, the httpclient module, and the auth module.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;in other words: WSGI sucks&lt;/p&gt;</description>
<dc:date>2009-09-11T06:50:35Z</dc:date>
<dc:author>greut</dc:author>
<dc:subject>web, use, server, http, wsgi, py, python</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.tornadoweb.org/documentation#wsgi-and-google-appengine"><img border="0" src="http://blogmarks.net/screenshots/2009/09/11/569b6e6bf9f6ee96d25543aab316a31a.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.tornadoweb.org/documentation#wsgi-and-google-appengine">Tornado Web Server Documentation</a></h4>
 
by <a href="http://blogmarks.net/user/greut">greut</a> 
<div class="description"><blockquote><p>Tornado comes with limited support for WSGI. However, since WSGI does not support non-blocking requests, you cannot use any of the asynchronous/non-blocking features of Tornado in your application if you choose to use WSGI instead of Tornado's HTTP server. Some of the features that are not available in WSGI applications: @tornado.web.asynchronous, the httpclient module, and the auth module.</p></blockquote>
<p>in other words: WSGI sucks</p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/use">use</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/http">http</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wsgi">wsgi</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/py">py</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/python">python</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058499632">Copy</a> | 
<a href="http://blogmarks.net/link/3339627">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Tiagut/mark/1058485281">
<title>Johan Mares » Installing Zend Server CE on Ubuntu</title>
<link>http://blog.johan-mares.be/ict/php/installing-zend-server-ce-on-ubuntu/</link>
<description>Tuto pour l'installation de Zend serve CE sur Ubuntu</description>
<dc:date>2009-08-29T13:54:55Z</dc:date>
<dc:author>Tiagut</dc:author>
<dc:subject>zend, server, ubuntu, tuto</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blog.johan-mares.be/ict/php/installing-zend-server-ce-on-ubuntu/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/29/a8ade0aa63e3e42242abbed3ea81e288.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blog.johan-mares.be/ict/php/installing-zend-server-ce-on-ubuntu/">Johan Mares » Installing Zend Server CE on Ubuntu</a></h4>
 
by <a href="http://blogmarks.net/user/Tiagut">Tiagut</a> 
<p class="description">Tuto pour l'installation de Zend serve CE sur Ubuntu</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/zend">zend</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ubuntu">ubuntu</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tuto">tuto</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058485281">Copy</a> | 
<a href="http://blogmarks.net/link/3327800">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/danijelzi/mark/1058472999">
<title>HP ProLiant ML150 G6 Tower Server Overview</title>
<link>http://getitequipped.com/hp-proliant-ml150-g6-generation-6-tower-server.html</link>
<description>Hewlett-Packard has released recently the HP ProLiant ML150 G6 Server series, a new 5U tower 2-socket system based on Intel’s new Nehalem CPU microarchitecture.

When compared to the Intel 5100 chipset-based ProLiant ML150 G5, the ML150 G6 (Generation 6) with the Intel 5500 chipset features newer Intel Xeon dual- or quad-core processors with integrated memory controllers, support for up to 48GB of DDR3 memory instead of up to 16GB DDR2, new controller and adapter options, a new chassis design, and other innovations.</description>
<dc:date>2009-08-19T17:08:15Z</dc:date>
<dc:author>danijelzi</dc:author>
<dc:subject>HP ProLiant ML150 G6, tower, server, intel, Nehalem, system</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://getitequipped.com/hp-proliant-ml150-g6-generation-6-tower-server.html"><img border="0" src="http://blogmarks.net/screenshots/2009/08/19/0c4fc45756eb356437d506f996fa9acf.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://getitequipped.com/hp-proliant-ml150-g6-generation-6-tower-server.html">HP ProLiant ML150 G6 Tower Server Overview</a></h4>
 
by <a href="http://blogmarks.net/user/danijelzi">danijelzi</a> 
<p class="description">Hewlett-Packard has released recently the HP ProLiant ML150 G6 Server series, a new 5U tower 2-socket system based on Intel’s new Nehalem CPU microarchitecture.

When compared to the Intel 5100 chipset-based ProLiant ML150 G5, the ML150 G6 (Generation 6) with the Intel 5500 chipset features newer Intel Xeon dual- or quad-core processors with integrated memory controllers, support for up to 48GB of DDR3 memory instead of up to 16GB DDR2, new controller and adapter options, a new chassis design, and other innovations.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/HP%2BProLiant%2BML150%2BG6">HP ProLiant ML150 G6</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tower">tower</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/intel">intel</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Nehalem">Nehalem</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/system">system</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058472999">Copy</a> | 
<a href="http://blogmarks.net/link/3320084">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Adri1bip/mark/1058463803">
<title>Mac4Ever.com • Voir le sujet - un serveur afp utilisable avec time machine sous debian</title>
<link>http://forum.mac4ever.com/un-serveur-afp-utilisable-avec-time-machine-sous-debian-t32626.html</link>
<description></description>
<dc:date>2009-08-24T10:01:27Z</dc:date>
<dc:author>Adri1bip</dc:author>
<dc:subject>afpd, debian, server, afp</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://forum.mac4ever.com/un-serveur-afp-utilisable-avec-time-machine-sous-debian-t32626.html"><img border="0" src="http://blogmarks.net/screenshots/2009/08/24/492327bf49ff95ebc6653afec51808ff.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://forum.mac4ever.com/un-serveur-afp-utilisable-avec-time-machine-sous-debian-t32626.html">Mac4Ever.com • Voir le sujet - un serveur afp utilisable avec time machine sous debian</a></h4>
 
by <a href="http://blogmarks.net/user/Adri1bip">Adri1bip</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/afpd">afpd</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/debian">debian</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/afp">afp</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058463803">Copy</a> | 
<a href="http://blogmarks.net/link/3312858">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/costel/mark/1058456631">
<title>Instalarea serverului de email Postfix în OpenSUSE Linux</title>
<link>http://www.blogospheerix.com/blog/it/entry/instalarea_serverului_email_postfix_opensuse</link>
<description>Articol in limba română despre instalarea serverului de mail Postfix în Opensuse Linux cu SMTP-AUTH şi TLS</description>
<dc:date>2009-08-06T17:20:00Z</dc:date>
<dc:author>costel</dc:author>
<dc:subject>serverde email Postfix, opensuse linux, postfix, instalare postfix, opensuse, linux, smtp-auth, tls, anti-spam, server, email, mail</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.blogospheerix.com/blog/it/entry/instalarea_serverului_email_postfix_opensuse"><img border="0" src="http://blogmarks.net/screenshots/2009/08/06/3c5ff4ef506a5026e8a3b7f578899303.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.blogospheerix.com/blog/it/entry/instalarea_serverului_email_postfix_opensuse">Instalarea serverului de email Postfix în OpenSUSE Linux</a></h4>
 
by <a href="http://blogmarks.net/user/costel">costel</a> 
<p class="description">Articol in limba română despre instalarea serverului de mail Postfix în Opensuse Linux cu SMTP-AUTH şi TLS</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/serverde%2Bemail%2BPostfix">serverde email Postfix</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opensuse%2Blinux">opensuse linux</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/postfix">postfix</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/instalare%2Bpostfix">instalare postfix</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opensuse">opensuse</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/smtp-auth">smtp-auth</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tls">tls</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/anti-spam">anti-spam</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/email">email</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mail">mail</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058456631">Copy</a> | 
<a href="http://blogmarks.net/link/3307733">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Xavier Lacot/mark/1058440964">
<title>libcloud python library - a unified interface cloud server providers</title>
<link>http://libcloud.org/</link>
<description>Libcloud is a standard client library for many popular cloud providers, written in python. Exactly what I talked about a few weeks ago when asking for a common API to all cloud server providers. Now search for a way to convert / move an image from one provider to another !</description>
<dc:date>2009-07-25T10:12:37Z</dc:date>
<dc:author>Xavier Lacot</dc:author>
<dc:subject>library, python, interface, server, virtualization, api, amazon, virtual, EC2, rackspace, slicehost</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://libcloud.org/"><img border="0" src="http://blogmarks.net/screenshots/2009/07/25/df37d0ce9307a7a25d7229df036153dd.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://libcloud.org/">libcloud python library - a unified interface cloud server providers</a></h4>
 
by <a href="http://blogmarks.net/user/Xavier Lacot">Xavier Lacot</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3294572">2 other(s)</a> 
<p class="description">Libcloud is a standard client library for many popular cloud providers, written in python. Exactly what I talked about a few weeks ago when asking for a common API to all cloud server providers. Now search for a way to convert / move an image from one provider to another !</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/library">library</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/python">python</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/interface">interface</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/virtualization">virtualization</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/api">api</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/amazon">amazon</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/virtual">virtual</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/EC2">EC2</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rackspace">rackspace</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/slicehost">slicehost</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058440964">Copy</a> | 
<a href="http://blogmarks.net/link/3294572">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/br1o/mark/1058556668">
<title>Wildcard DNS and Sub Domains — Matt Mullenweg</title>
<link>http://ma.tt/2003/10/wildcard-dns-and-sub-domains/</link>
<description></description>
<dc:date>2009-07-21T16:55:10Z</dc:date>
<dc:author>br1o</dc:author>
<dc:subject>wordpress_mu, wildcarddns, config, subdomain, wpmu, wordpressmu, sysadmin, mu, buddypress, WP, howto, webdev, apache, domain, dns, Domains, server, reference, wordpress, webdesign, subdomains, wildcard, redirect</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://ma.tt/2003/10/wildcard-dns-and-sub-domains/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://ma.tt/2003/10/wildcard-dns-and-sub-domains/">Wildcard DNS and Sub Domains — Matt Mullenweg</a></h4>
 
by <a href="http://blogmarks.net/user/br1o">br1o</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wordpress_mu">wordpress_mu</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wildcarddns">wildcarddns</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/config">config</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/subdomain">subdomain</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wpmu">wpmu</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wordpressmu">wordpressmu</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sysadmin">sysadmin</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mu">mu</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/buddypress">buddypress</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/WP">WP</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/howto">howto</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdev">webdev</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apache">apache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/domain">domain</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dns">dns</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Domains">Domains</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/reference">reference</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wordpress">wordpress</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdesign">webdesign</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058556668">Copy</a> | 
<a href="http://blogmarks.net/link/3389070">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/newandforever/mark/1058398590">
<title>process server anaheim</title>
<link>http://viselka.com/Orange_County-6.htm</link>
<description>process server anaheim</description>
<dc:date>2009-07-02T20:56:37Z</dc:date>
<dc:author>newandforever</dc:author>
<dc:subject>server, Anaheim, process server anaheim, sashatornadova, process</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://viselka.com/Orange_County-6.htm"><img border="0" src="http://blogmarks.net/screenshots/2009/07/02/f195dd672a437002d27dc53ce4a07dca.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://viselka.com/Orange_County-6.htm">process server anaheim</a></h4>
 
by <a href="http://blogmarks.net/user/newandforever">newandforever</a> 
<p class="description">process server anaheim</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Anaheim">Anaheim</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/process%2Bserver%2Banaheim">process server anaheim</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sashatornadova">sashatornadova</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/process">process</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058398590">Copy</a> | 
<a href="http://blogmarks.net/link/3259830">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/delavigne/mark/1058383789">
<title>Ignite Realtime: Openfire Server</title>
<link>http://www.igniterealtime.org/projects/openfire/index.jsp</link>
<description></description>
<dc:date>2009-06-21T20:27:41Z</dc:date>
<dc:author>delavigne</dc:author>
<dc:subject>server, chat, wmpp, jabber</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.igniterealtime.org/projects/openfire/index.jsp"><img border="0" src="http://blogmarks.net/screenshots/2009/06/21/7b89a8e049a597b75a12a90be9d0ee23.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.igniterealtime.org/projects/openfire/index.jsp">Ignite Realtime: Openfire Server</a></h4>
 
by <a href="http://blogmarks.net/user/delavigne">delavigne</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2188433">2 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/chat">chat</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wmpp">wmpp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/jabber">jabber</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058383789">Copy</a> | 
<a href="http://blogmarks.net/link/2188433">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/br1o/mark/1058556780">
<title>Trick Out Your CSS With Server Side Code | Design Reviver</title>
<link>http://designreviver.com/tips/trick-out-your-css-with-server-side-code/</link>
<description></description>
<dc:date>2009-06-20T23:12:11Z</dc:date>
<dc:author>br1o</dc:author>
<dc:subject>php, css, colors, server, variables, css-php, side, webdesign, tutorials</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://designreviver.com/tips/trick-out-your-css-with-server-side-code/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://designreviver.com/tips/trick-out-your-css-with-server-side-code/">Trick Out Your CSS With Server Side Code | Design Reviver</a></h4>
 
by <a href="http://blogmarks.net/user/br1o">br1o</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/colors">colors</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/variables">variables</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css-php">css-php</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/side">side</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdesign">webdesign</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutorials">tutorials</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058556780">Copy</a> | 
<a href="http://blogmarks.net/link/3389148">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058379897">
<title>Shindig - Welcome To Shindig!</title>
<link>http://incubator.apache.org/shindig/</link>
<description>What is Shindig?
Shindig is a container for hosting social application consisting of four parts:

    * Gadget Container JavaScript: core JavaScript foundation for general gadget functionality (read more about gadget functionality). This JavaScript manages security, communication, UI layout, and feature extensions, such as the OpenSocial API.
    * Gadget Rendering Server: used to render the gadget XML into JavaScript and HTML for the container to expose via the container JavaScript.
    * OpenSocial Container JavaScript: JavaScript environment that sits on top of the Gadget Container JavaScript and provides OpenSocial specific functionality (profiles, friends, activities, datastore).
    * OpenSocial Data Server: an implementation of the server interface to container-specific information, including the OpenSocial REST APIs, with clear extension points so others can connect it to their own backends.

Shindig is the reference implementation of OpenSocial API specifications, a standard set of Social Network APIs which includes:

    * Profiles
    * Relationships
    * Activities
    * Shared applications
    * Authentication
    * Authorization</description>
<dc:date>2009-06-19T20:41:01Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>network, application, server, api, xml, social network, apache, OpenSocial, clevermarks</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://incubator.apache.org/shindig/"><img border="0" src="http://blogmarks.net/screenshots/2009/06/19/33b674bef9b2ce6a3924896402e03e23.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://incubator.apache.org/shindig/">Shindig - Welcome To Shindig!</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2660069">4 other(s)</a> 
<p class="description">What is Shindig?
Shindig is a container for hosting social application consisting of four parts:

    * Gadget Container JavaScript: core JavaScript foundation for general gadget functionality (read more about gadget functionality). This JavaScript manages security, communication, UI layout, and feature extensions, such as the OpenSocial API.
    * Gadget Rendering Server: used to render the gadget XML into JavaScript and HTML for the container to expose via the container JavaScript.
    * OpenSocial Container JavaScript: JavaScript environment that sits on top of the Gadget Container JavaScript and provides OpenSocial specific functionality (profiles, friends, activities, datastore).
    * OpenSocial Data Server: an implementation of the server interface to container-specific information, including the OpenSocial REST APIs, with clear extension points so others can connect it to their own backends.

Shindig is the reference implementation of OpenSocial API specifications, a standard set of Social Network APIs which includes:

    * Profiles
    * Relationships
    * Activities
    * Shared applications
    * Authentication
    * Authorization</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/network">network</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/application">application</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/api">api</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xml">xml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/social%2Bnetwork">social network</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apache">apache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/OpenSocial">OpenSocial</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/clevermarks">clevermarks</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058379897">Copy</a> | 
<a href="http://blogmarks.net/link/2660069">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/eaque/mark/1058368838">
<title>SVI-wiki: Scp Batch Mode</title>
<link>http://support.svi.nl/wiki/ScpBatchMode</link>
<description>done with a regular (with password) ssh connection, and accepting the host as known. Then, the host name should be the same as the one</description>
<dc:date>2009-06-17T16:13:13Z</dc:date>
<dc:author>eaque</dc:author>
<dc:subject>openssh, ssh, unix, server</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://support.svi.nl/wiki/ScpBatchMode"><img border="0" src="http://blogmarks.net/screenshots/2009/06/17/a89ef9cae56af9a79d58282a6af9c61f.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://support.svi.nl/wiki/ScpBatchMode">SVI-wiki: Scp Batch Mode</a></h4>
 
by <a href="http://blogmarks.net/user/eaque">eaque</a> 
<p class="description">done with a regular (with password) ssh connection, and accepting the host as known. Then, the host name should be the same as the one</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/openssh">openssh</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ssh">ssh</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unix">unix</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058368838">Copy</a> | 
<a href="http://blogmarks.net/link/3234381">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Giraultises/mark/1058357010">
<title>Synchroniser vos bookmarks et mots de passe sur plusieurs ordinateurs et sur serveur</title>
<link>http://www.xmarks.com/</link>
<description>Xmarks est un add-in pour Firefox, IE et Safari qui vous permettra de synchroniser vos bookmarks et vos mots de passe entre vos ordinateurs. Vous pourrez aussi synchroniser ces derniers sur votre propre serveur.</description>
<dc:date>2009-06-10T10:30:29Z</dc:date>
<dc:author>Giraultises</dc:author>
<dc:subject>mot de passe, bookmark, ie, safari, firefox, addon, extension, server</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.xmarks.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/25/f0f4ce7435043ebf6471179dfce84249.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.xmarks.com/">Synchroniser vos bookmarks et mots de passe sur plusieurs ordinateurs et sur serveur</a></h4>
 
by <a href="http://blogmarks.net/user/Giraultises">Giraultises</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3115093">3 other(s)</a> 
<p class="description">Xmarks est un add-in pour Firefox, IE et Safari qui vous permettra de synchroniser vos bookmarks et vos mots de passe entre vos ordinateurs. Vous pourrez aussi synchroniser ces derniers sur votre propre serveur.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mot%2Bde%2Bpasse">mot de passe</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bookmark">bookmark</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ie">ie</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/safari">safari</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/firefox">firefox</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/addon">addon</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/extension">extension</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058357010">Copy</a> | 
<a href="http://blogmarks.net/link/3115093">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/RETFU/mark/1058356765">
<title>Union Platform Overview • The Union Platform, By User1</title>
<link>http://www.unionplatform.com/?page_id=30</link>
<description></description>
<dc:date>2009-06-10T08:15:12Z</dc:date>
<dc:author>RETFU</dc:author>
<dc:subject>server, realtime</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.unionplatform.com/?page_id=30"><img border="0" src="http://blogmarks.net/screenshots/2009/06/10/843953751f0c580b63bedbbfab398c11.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.unionplatform.com/?page_id=30">Union Platform Overview • The Union Platform, By User1</a></h4>
 
by <a href="http://blogmarks.net/user/RETFU">RETFU</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/realtime">realtime</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058356765">Copy</a> | 
<a href="http://blogmarks.net/link/3224623">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>