Feed aggregator

On Feb 17, 2012, at 3:13 PM, Boris Okner wrote: It did help! Thanks a lot! Regards, -- Saúl Ibarra Corretgé AG Projects

Try: NewPacket = xml:append_subtags(Packet, [XmlTo]), ..... instead of : NewPacket = xml:append_subtags(Packet, XmlTo), xml:append_subtags/2 accepts the list of tags as a 2nd parameter as opposed to a single tag. Hope this helps, Boris Okner On Fri, Feb 17, 2012 at 3:19 AM, Saúl Ibarra Corretgé <saul< at >ag-projects.com> wrote:

Hi all, I'm trying to achieve something I believe it's quite simple, but my lack of knowledge of Erlang (just started) could be playing me here. I basically want to add a custom element to a message stanza when I get it in an offline_message hook. This is the simplest possible code that is failing for me: ... XmlTo = {xmlelement,"agp:foo", [{"value", "bar"}, {"xmlns:agp","ag-projects:xmpp"}], []}, NewPacket = xml:append_subtags(Packet, XmlTo), ... ejabberd_router:route(_From, Destination, NewPacket), This gives me a badxml error: ** {{badxml, {xmlelement,"message", [{"from","saghul< at >gmail.com/Psi+4A1A4569"}, {"to","saghul< at >a.b.c.d"}, {"type","chat"}, {"id","a2298a"}], [{xmlcdata,<<"\n">>}, {xmlelement,"body",[],[{xmlcdata,<<"t">>}]}, {xmlcdata,<<"\n">>}, {xmlelement,"active", [{"xmlns","http://jabber.org/protocol/chatstates"}], []}, {xmlcdata,<<"\n">>}, {xmlelement,"request",[{"xmlns","urn:xmpp:receipts"}],[]}, {xmlcdata,<<"\n">>}, {xmlelement,"nos:x", [{"value","disabled"},{"xmlns:nos","google:nosave"}], []}, {xmlelement,"arc:record", [{"otr","false"},{"xmlns:arc","http://jabber.org/protocol/archive"}], []}| {xmlelement,"agp:foo", [{"value","bar"},{"xmlns:agp","ag-projects:xmpp"}], []}]}, {function_clause, [{xml,'-element_to_string_nocatch/1-lc$^0/1-0-', [{xmlelement,"agp:foo", [{"value","bar"},{"xmlns:agp","ag-projects:xmpp"}], []}]}, {xml,'-element_to_string_nocatch/1-lc$^0/1-0-',1}, {xml,element_to_string_nocatch,1}, {xml,element_to_string,1}, {xml,element_to_binary,1}, {ejabberd_service,handle_info,3}, {p1_fsm,handle_msg,10}, {proc_lib,init_p_do_apply,3}]}}, [{xml,element_to_string,1}, {xml,element_to_binary,1}, {ejabberd_service,handle_info,3}, {p1_fsm,handle_msg,10}, {proc_lib,init_p_do_apply,3}]} I guess it's a simple mistake, but I can't seem to find it :-S any help would be appreciated. In case it matters this is ejabberd 2.1.10. Thanks and regards, -- Saúl Ibarra Corretgé AG Projects

Since launching M-Link, our XMPP server, we’ve been asked by many organisations if we can supply and support both server and client components of an XMPP solution.

While Isode remains primarily focused on server software, we’ve teamed up with the developers of the Swift XMPP client to offer commercial support contracts for Swift installations. A lot of Isode staff use Swift as their preferred client (it’s free, open source and is available on Windows, Mac OS X and Linux) and we’ve been recommending Swift in our evaluation guides for some time.

Swift has been partly developed by one of Isode’s engineering team and as a company we have contributed engineering resources to its development, something we intend to continue. In addition we’re also now offering commercial licences and support for the Swiften XMPP Client Library. Swiften is used as the back-end library for Swift.

For more information please contact Isode.

On Tue, Feb 14, 2012 at 10:04 PM, James Iakovos Mandelis <ebuggerd< at >008.clara.co.uk> wrote: You add SRV record to your DNS server and do nothing to ejabberd.cfg (assuming it is set up correctly already) Google "SRV record for xmpp server." Essentially if gmail server looks up srv record for _xmpp-server._tcp.yourdomain.com it should tell gmail server which ipaddress and port to use to deliver messages to your domain. By default ejabberd uses port 5269 for server to server communication; but it can be changed in your ejabberd.cfg

Google Talk supports regular server-to-server federation; if you have that turned on, you'll be able to exchange messages just fine (barring what appears to be a policy about dropping incoming messages that aren't roster adds unless the source is in the destination's roster). As for testing, any mail account < at >gmail.com or < at >googlemail.com is automatically a Gtalk account, so if you have one you can log in with your favourite XMPP client. Or ask a friend who uses GTalk to help.

Hi, I need to connect ejabberd to Gtalk. How do I change the ejabberd.cfg file and how do I test the connection? Thanks

Ejabberd freecarraceinggames? Eh151fxr cheb_nasro_2009rar ccleaner? Reversphone aquaform costablanca hothorney freedownloadultimatehackv211_serialrar france profonde kellerdolce www bayw org calvin ruggerodp discografia ...

While megaphone is marginally aware of the nature of HTTP, in that it has use erlang:decode_packet on the data that it hands off to ejabberd when it sends data back to the client it has no idea if this is a response to an HTTP request - it's just ...

Hi all, We have a project where we'd like to integrate ejabberd with an existing system based on MongoDB. I've seen approaches to running ejabberd over Mongo which involve an ODBC wrapper, but I'd like to avoid that -- it strikes me as inefficient (and complicated!), and involves using a highly relational schema in Mongo, which it isn't well-suited for. Instead, we'd like to write a new gen_storage backend, implementing the same API as gen_storage_odbc and translating queries to native Mongo calls. That part seems fairly easy, but there are places in the ejabberd code that explicitly check backend names (e.g. gen_storage:create_table, and one place in gen_storage:table_info which looks like a bug). I also notice that mod_pubsub seems to have two completely parallel implementations, one for mnesia and one for odbc, which duplicate code rather than abstracting backend calls out via gen_storage. I can't immediately see a reason for this. So, we'd like to write a patch for ejabberd which does the following: - Minor tweaks to gen_storage to allow custom backends in places like create_table - Minor tweaks to other hardcoded backend references (e.g. mod_roster:update_table) to allow the same. - Major refactoring of mod_pubsub to abstract out storage calls, either via gen_storage or by splitting it into e.g. mod_pubsub, mod_pubsub_storage_mnesia, and mod_pubsub_storage_odbc, and then allowing alternate backends to be injected. If we do this, what are our chances of getting it merged into trunk? Are there major problems that I haven't anticipated, or existing work in the same direction? Cheers, Brendon Hogger Cogini

Yay!

These last days, we focused our development on Jappix Mini, a great website mini-chat provided in the Jappix package. You can try the old Jappix Mini version on the demo website - and add it to your own website if you like it!

Let's sum up what will appear in 0.9.1 Jappix release for Jappix Mini:



We would like to thanks both hunterjm and allan for their buddy sorting and searching patch (see commit diff and submitted patch).

The next Jappix version - Jappix Spaco Unu (0.9.1) - will be soon released, once the last features we planned will be coded and everything debugged!

Vanaryon, Jappix founder.

While I have a nagging belief that saying that something is working will immediately cause the code gremlins to break everything, I finally managed to get the receive portion of the Megaphone tests to at least look like they are working!

This is because in languages like erlang, you cannot change a variable once it has been set. Personally, I don't think one should use the term "variable" to describe such an object in erlang, but I digress. The problem I was running into was ...

5，Erlang. The language was born several years, in various areas of development are good. Like XMPP (specifically should be the eJabberd), PubSubHubbub, real-time technology for continued growth 2011, its ranking might next to Python.

It includes ejabberd and thus has an XMPP chat server. You can connect to this with XMPP clients like gajaim, pidgin and finch. I use finch as I like TUI/CLI mode. It might be like mcabber. You can setup 'autoconnect' chats. You can setup ...

openfire vs ejabberd OpenBSD Packages and Ports.

I'm still working on jingleFT for Gajim (not much progress there). The changes for xep-135 (no progress at all there). A secret project involving i2p (I don't talk about projects before having done a beta. No much progress there either).

The jingleFT branch of Gajim does need some refactoring. I made a state diagram of the file transfer, and it looks awful.



Clearly there are unnecessary states like transport info and proxy activated. The events are somewhat ambiguous, and the states accepted and initialized should be merged into one.

I'll fix it. See if I can shake off being so stalled.

Hi boys and girls I have finished publish and subscribe function on pubsub(0060) with exmpp . Although It have not comment function. There is comment function in the microblog( exp-0027) . I want to only use comment of microblog ( only using 3. Comments 3.1. Post Comments not using 2.3. Publishing a Post 2.4. Receiving a Post 2.5. Replying to a Post 2.6. Repeating a Post 2.7. Attaching files to a Post), but i am not sure what it is work . Please give some advice to me. Thank everybody. Jason_______________________________________________ ejabberd mailing list ejabberd< at >jabber.ru http://lists.jabber.ru/mailman/listinfo/ejabberd

Many of you have followed the launch of the ProcessOne Push Platform (P1PP) in our webinar. Thanks a lot! Here are a few tools that make PubSub a reality.

Our P1PP (ProcessOne Push Platform) has gone live: the dedicated PubSub XMPP service has finally become a reality, as we launched it during our webinar. Here is a short presentation.

P1PP in short

P1PP is mainly an open federated platform for "PubSub, the good parts", or "PubSub made easy". For now, it is mainly designed for developers:

For developers and XMPP geeks:

Webinar slides ProcessOne Push Platform: pubsub.p1pp.net View more presentations from ProcessOne Please comment!

We are waiting for your comments. So feel free to express your needs!

Stay tuned as we have more.

Many of you have followed the launch of the ProcessOne Push Platform (P1PP) in our webinar. Thanks a lot! Here are a few tools that make PubSub a reality.

Our P1PP (ProcessOne Push Platform) has gone live: the dedicated PubSub XMPP service has finally become a reality, as we launched it during our webinar. Here is a short presentation.

P1PP in short

P1PP is mainly an open federated platform for "PubSub, the good parts", or "PubSub made easy". For now, it is mainly designed for developers:

For developers and XMPP geeks:

Webinar slides ProcessOne Push Platform: pubsub.p1pp.net View more presentations from ProcessOne Please comment!

We are waiting for your comments. So feel free to express your needs!

Stay tuned as we have more.