[Twisted-Python] Information on new endpoints API?
Tom Davis
tom at recursivedream.com
Mon Jun 13 09:02:45 EDT 2011
On Jun 13, 2011, at 8:26 AM, exarkun at twistedmatrix.com wrote:
> On 12 Jun, 01:34 pm, orestis at orestis.gr wrote:
>>> This is really why we introduced endpoints - to make it possible for
>>> applications to listen on (or connect to) an address that is specified
>>> elsewhere. Previously, the "easy thing to do" was to only support
>>> TCP/IPv4. With endpoints, the "easy thing to do" is to work with any
>>> address family/transport type that there is now (or will be in the
>>> future!) an endpoint for.
>>
>> That's a perfect explanation, many thanks!
>>>> I will be giving a training on Twisted in a few days during the
>>>> EuroPython conference (actually, more of an assisted tutorial than a
>>>> training) and I'm not sure how I should present this. Any information
>>>> would be helpful.
>>>>
>>>> Orestis
>>>
>>> Hope this helps! Good luck with the session. :)
>>
>> Thanks. BTW, I've spent the past week browsing through twisted's
>> documentation (esp. the API reference). I have a few ideas that I think
>> would help newcomers find their away around much easier (and be less
>> scared of twisteD). The ideas are mostly organisational, the material
>> is there, if one knows what to look for. Should I create new tickets or
>> mail ideas to this list?
>
> It would probably be best if you could get Kevin Horn and/or Tom Davis'
> attention. They've both been thinking about making the documentation
> more accessible lately. It would be great to incorporate your ideas
> into the overall plan.
My ears, they burn! But, yeah, in terms of discoverability, the ever-near lore-to-Sphinx conversion does a ton for discoverability and makes obvious a number of opportunities for organizational improvement (a link to a recentish build eludes me, but when you seem them you'll know what I mean). Beyond the low-hanging fruit, there are many notes regarding individual docs improvements. Feel free to share your own, though I recommend checking Trac first because many documents do indeed have tickets. If you need help there let me know.
Speaking of the lore-to-Sphinx conversion, I am contractually obligated to inform you that improvements to current documentation is not blocked by the pending conversion. And that you have the right to a lawyer.
Cheers,
Tom
> Jean-Paul
>
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
More information about the Twisted-Python
mailing list