search

pgstath / Sharp.Xmpp

Sharp.Xmpp is looking for a maintainer! Unfortunatelly I do not have currently the time needed to maintain the library. Luckily a small but vibrant community has evolved around Sharp.Xmpp. If you would like to be the project's maintainer please sent an email to pgstath@gmail.com. This should include issues, tickets and commits that you have done for Sharp.Xmpp or other similar project. Sharp.Xmpp is a multiplatform, Windows and Android, .NET XMPP client assembly.Sharp.Xmpp supports IM functionality & a variety of XMPP extensions, is simple and is extensively tested against Android Xamarin. It is a fork of the currently frozen excellent S22.Xmpp project. Sharp.Xmpp will be at the FOSSDEM 2016 Real time DevRoom!
Other
84 stars 51 forks source link

Disable SRV resolution #7

Closed DavePilks closed 8 years ago

DavePilks commented 9 years ago

Hi

Is there a way that I can manually declare my hostname separately from him XMPP domain so as to avoid an SRV DNS lookup?

pgstath commented 9 years ago

Hello, For the time beeing no, ideally DNS should be configured appropriately. There is a merge request that accomplishes what you propose (with IP addresses). You are wishing for this functionality in order to use if for testing mainly? This could be included in a next version.

DavePilks commented 9 years ago

HI,

For the time being yes. I am trying to put together a Proof of Concept for my company and am thus using Windows Azure and their hosting. This makes setting up the DNS and SRV records a little tough and not worth the time for a PoC. If it could be included, that would be great and really appreciated.

DavePilks commented 9 years ago

Is there any ETA on a new release?

pgstath commented 9 years ago

Based on the interest on this feature, from other persons also, an estimated ETA for this feature is the end of September.

pgstath commented 9 years ago

You can try https://github.com/pgstath/Sharp.Xmpp/tree/dev-rafaneri branch, it is contribution by a third party developer, that I am considering merging into the next version. It addresses the issue that you mentioned.