Renaming of the API

[SonyAPILib]

Due to the new capabilities and functions of this API Library, and with the addition of the device services, this API is becoming more DLNA specific, and not just Sony specific.

With the addition of AVTransport, Connection Manager, Media Services, Rendering Control and such, this API will be able to be used with other devices other than just Sony.

So, with this said, I am considering changing the name completely, and moving this project to a completely new one.

I will attempt to fix any bugs still present in the 5.1 version of the SonyAPILib so it will remain "AS-IS" and can still be used by anyone who has developed against it.

I am considering the new name to be something more like: "DLNAapiLib".

The name change will not change that much in the API, other than any reference to "Sony".

For example:

SonyDevice object will become a DLNADevice object.

SonyCommandList will become DLNACommandList

SonyOption will become DLNAOption

SonyCookie will become DLNACookie

The _mySony object will no longer be used in the new API.

I feel this will be a good start to get this API a little more recognition,  and could be more usable to more users.

Please let me know your thoughts on this, as I have not released any of the new code as of yet, but will be testing what I have this week.

Thanks to everyone for your participation and help!

 

[mattias...@gmail.com]

I have only had a peek at the source code yet, but looks like you put a lot of work into this. How is the new project you speak of coming along?

One wish if you do a reboot of the whole project is that you align it with the naming guidelines for .NET. E.g. upper camel-case for method names and no all-caps acronyms.

[SonyAPILib]

@mattias.online,

Please feel free to visit my GitHub site here: https://github.com/KHerron/SonyAPILib to see more recent information, or to keep up with the progress of this project.

5.2 has been completed for a while, and here you can see the Wiki pages for more detailed information.

I apologize for the naming being all over the place. As in the beginning, a lot of my code was based or received from other sources (Java script, Python, Ruby, Pearl), and I kept the same naming used in the examples and resource code I retrieved. I always meant to go back through and correct this, but it seemed the project got very large, very fast! However, with that said, I do plan to start working on 5.3, that will probably have a release date closer to the end of this year, but I will definitely add it to the to do list. See here: https://github.com/KHerron/SonyAPILib/issues.

Thank you for your interest, and please let me know if you had any other issues.