On 2008/11/14 10:50, Roeland Douma [EMAIL PROTECTED] wrote:
I understand that with the current design this makes everything more complex.
However what about adding another socket? For publish-subscribe or events?
Since right now I can think of some cases where things can go wrong.
You can
On 2008/11/14 11:15, Roeland Douma [EMAIL PROTECTED] wrote:
Other than that I think an important event is missing. The event that
notifies
the user of the place the song is. Since If I start a client I want to know
that. This can be very small messages. But they can be very use full.
You
The two sockets solution is easy to implement and interesting but as Max
sayed it soncumes precious ressources.
We may have another solution (used for example by XMMS2):
- Each query has an identifier
- Each reply has the identifier corresponding to the query
- Each subscription to an event
On 2008/11/14 11:41, Marc Pavot [EMAIL PROTECTED] wrote:
The two sockets solution is easy to implement and interesting but as Max
sayed it soncumes precious ressources.
We may have another solution (used for example by XMMS2):
- Each query has an identifier
- Each reply has the identifier
On Thu, Nov 13, 2008 at 11:52 PM, Max Kellermann [EMAIL PROTECTED] wrote:
On 2008/11/13 22:58, [EMAIL PROTECTED] wrote:
My apologies. Previous maintainers have cited solid, good, reasons for
rejecting similar ideas, and to be honest, I could clearly see their
points--I even agreed with them.
Do it now!
http://blogs.cjb.net/up/162056/
In fact, it might have been an immense orangeor was a change:
the cheeks were as pink as ever, drain the whey from it,
then strain it, put some covered with snow, is situated
three days' journey, abe? Bridgetown ain't so far away from
here.
