<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic could STLClient be serializable? in Tools</title>
    <link>https://community.cisco.com/t5/tools/could-stlclient-be-serializable/m-p/3567589#M378</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi developers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to add trex to my automation tool, which is built with django.&lt;/P&gt;&lt;P&gt;In my use, each stlclient is specific to users and I tried to store it to sessions.&lt;/P&gt;&lt;P&gt;However, it failed.&lt;/P&gt;&lt;P&gt;The ways I have tried is json.dumps() and pickle.dumps().&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you know any other ways for this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Yufeng.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 Sep 2017 08:34:59 GMT</pubDate>
    <dc:creator>yufenwan</dc:creator>
    <dc:date>2017-09-21T08:34:59Z</dc:date>
    <item>
      <title>could STLClient be serializable?</title>
      <link>https://community.cisco.com/t5/tools/could-stlclient-be-serializable/m-p/3567589#M378</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi developers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to add trex to my automation tool, which is built with django.&lt;/P&gt;&lt;P&gt;In my use, each stlclient is specific to users and I tried to store it to sessions.&lt;/P&gt;&lt;P&gt;However, it failed.&lt;/P&gt;&lt;P&gt;The ways I have tried is json.dumps() and pickle.dumps().&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you know any other ways for this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Yufeng.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Sep 2017 08:34:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/tools/could-stlclient-be-serializable/m-p/3567589#M378</guid>
      <dc:creator>yufenwan</dc:creator>
      <dc:date>2017-09-21T08:34:59Z</dc:date>
    </item>
    <item>
      <title>Re: could STLClient be serializable?</title>
      <link>https://community.cisco.com/t5/tools/could-stlclient-be-serializable/m-p/3567590#M379</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Btw you last suggestion regarding the Stream object was released in v2.30.&lt;/P&gt;&lt;P&gt;Regarding this question. There is no need to serialized client as it does &lt;STRONG&gt;not&lt;/STRONG&gt; have it’s own information it is always sync with the server!&lt;/P&gt;&lt;P&gt;So you just need to save the destination TRex server IP. once you try to connect to the server it will sync.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hanoh&lt;/P&gt;&lt;P&gt;Sent from my iPhone&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Sep 2017 17:03:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/tools/could-stlclient-be-serializable/m-p/3567590#M379</guid>
      <dc:creator>hhaim@cisco.com</dc:creator>
      <dc:date>2017-09-23T17:03:32Z</dc:date>
    </item>
  </channel>
</rss>

