Yes, I am going to make in in 2.15.0.
Well, one more question: Shall we keep libohtcpconnx name for transport
library?
I think that libopenhpitransport or libopenhpitransport_tcp are more clear.
Current libriries:
[~/trunk/lib] ls -1 *.so
libohtcpconnx.so
libohudpconnx.so
libopenhpi.so
libopenhpi_snmp.so
libopenhpi_ssl.so
libopenhpimarshal.so
libopenhpiutils.so
What say?
Anton Pak
On Fri, 21 May 2010 18:57:12 +0400, Bishop, Michael (ISB Linux/Telco)
<[email protected]> wrote:
> Anton -
>
> Those changes are fine with me. Are you planning to include them in
> 2.15.0 (sheduled for late-June 2010)??
>
> --michael
>
> Regards,
> Michael Bishop
> Enterprise Servers and Storage (ISB Linux/Telco)
> Hewlett-Packard Company
> 3404 E. Harmony Rd. Bldg. 5L, Post B7, Mailstop 42
> Fort Collins, CO 80528-9599
> Phone: 970-898-4393
> E-Mail: [email protected]
>
>
>> -----Original Message-----
>> From: Anton Pak [mailto:[email protected]]
>> Sent: Friday, May 21, 2010 5:30 AM
>> To: OpenHPI-devel
>> Subject: [Openhpi-devel] Marshal and transport topics
>>
>>
>> Hello all!
>>
>> Could you please review and comment feature requests #3005257
>> and #3005255.
>> I am sure there are UDP transport advocates but the code is really
>> unusable now and
>> work need to be done to revive it.
>>
>> Anton Pak
>>
>> --------------------------------------------------------------
>> ----------------
>>
>> _______________________________________________
>> Openhpi-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/openhpi-devel
>>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Openhpi-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openhpi-devel
------------------------------------------------------------------------------
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
