jwchat-devel — Development

[Jwchat-devel] Fwd: [CFP] FOSDEM 2021, RTC devroom, speakers, volunteers neeeded

[FOSDEM R. T. <fos...@fr...>]

FOSDEM - Real Time Communications devroom CfP
=============================================

NOTE: we have extended the deadline but we will give preference
to people who submitted earlier when we set the time for each
talk.  Please submit your proposal ASAP so that you can get
your preferred time slot.

Overview
--------

[FOSDEM](https://fosdem.org) is one of the world's premier meetings of
free software developers, with over five thousand people attending each
year. FOSDEM 2021 takes place 6-7 February 2021 and for the very first
time, it will be online.

This document contains information about:

-   Real-Time Communications developer room (devroom)
-   speaking opportunities
-   volunteering

New rules for the online edition
--------------------------------

This year FOSDEM will be fully online instead of being held in Brussels,
here are the most important things to know about this (quite
significant) change:

-   The reference time will be Brussels local time (CET)
-   Talks will be pre-recorded in advance, and streamed during the event
-   The Q/A session will be live
-   A facility will be provided for people watching to chat between
    themselves
-   A facility will be provided for people watching to submit questions

Call for participation - Real Time Communications (RTC)
-------------------------------------------------------

The Real-Time devroom is about all things involving real-time
communication, including: XMPP, SIP, WebRTC, telephony, mobile VoIP,
codecs, peer-to-peer, privacy and encryption.

**We are looking for speakers for the devroom and volunteers who can
help manage the scheduling and live Q&A sessions.**

The devroom is only on Saturday, 6th of February 2021.

To discuss the devroom, volunteer or ask questions, please join the
[Free-RTC mailing
list](http://lists.freertc.org/mailman/listinfo/discuss).

### Key dates

-   20th Dec: Submission deadline (extended to 8 January)
-   24th Dec: Announcement of selected talks
-   15th Jan: Presentations upload deadline
-   6th & 7th Feb: Conference dates (online)
-   6th Feb: RTC devroom date (online)

### Speaking opportunities

Note: if you used FOSDEM Pentabarf before, please use the same
account/username

Real-Time Communications devroom: deadline 23:59 UTC on 20th of
December. Please use the
[Pentabarf](https://penta.fosdem.org/submission/FOSDEM21/) system to
submit a talk proposal for the devroom. On the "General" tab, please
look for the "Track" option and choose "Real Time Communications
devroom".

### First-time speaking?

FOSDEM devrooms are a welcoming environment for people who have never
given a talk before. Please feel free to contact the devroom
administrators personally if you would like to ask any questions about
it.

This year this is more true than ever, being able to record your
presentation offline without an audience in front can greatly help build
up one's confidence!

### Submission guidelines

The Pentabarf system will ask for many of the essential details. Please
remember to re-use your account from previous years if you have one.

In the "Submission notes", please tell us about:

-   The purpose of your talk
-   Any other talk applications (devrooms, lightning talks, main track)
-   Availability constraints and special needs

You can use HTML and links in your bio, abstract and description.

If you maintain a blog, please consider providing us with the URL of a
feed with posts tagged for your RTC-related work.

We will be looking for relevance to the conference and devroom themes,
presentations aimed at developers of free and open source software about
RTC-related topics.

Please feel free to suggest a duration between 20 minutes and 55 minutes
but note that the final decision on talk durations will be made by the
devroom administrators based on the number of received proposals. As the
two previous devrooms have been combined into one, we may decide to give
shorter slots than in previous years so that more speakers can
participate.

Please note FOSDEM aims to record and live-stream all talks. The CC-BY
license is used.

### Recording help

The devroom organization is able to provide help with recording your
session. The recording would be performed at a scheduled time with one
of us, so you won't be alone giving your presentation. Minimal edits
will be possible, but the ideal plan is to record it in one shot.

Thanks Dan Jenkins for providing us with the means to do this!

Volunteers needed
-----------------

To make the devroom run successfully, we are looking for volunteers.
This year many things be done for the first time, so all the help we can
get is more than welcome.

Spread the word and discuss
---------------------------

If you know of any mailing lists where this CfP would be relevant,
please forward this document. If this devroom excites you, please blog
or microblog about it, especially if you are submitting a talk.

If you regularly blog about RTC topics, please send details about your
blog to the planet site administrators:

-   All projects https://planet.freertc.org pl...@fr...
-   XMPP https://planet.jabber.org ra...@ik...
-   SIP https://planet.sip5060.net pl...@si...

Please also link to the Planet sites from your own blog or web site as
this helps everybody in the free real-time communications community.

Contact
-------

For any private queries, contact us directly using the address
**fos...@fr...** and for any other queries please ask on
the [Free-RTC mailing
list](http://lists.freertc.org/mailman/listinfo/discuss).

The devroom administration team:

-   Saúl Ibarra Corretgé <s...@sa...>
-   Ralph Meijer <ra...@ik...>
-   Daniel-Constantin Mierla <mi...@gm...>
-   Daniel Pocock <da...@po...>
-   Guus der Kinderen <guu...@gm...>

[Jwchat-devel] [CFP] reminder! FOSDEM RTC dev-room talks: deadline tomorrow

[FOSDEM R. T. <fos...@fr...>]

Reminder: speaker's deadline tomorrow, 17 November at 23:59 UTC

The Free RTC dev-room has already received some really exciting
talk proposals but there is still time for people to propose talks or
encourage friends or colleagues to speak.

Many other dev-rooms also have a deadline in the next few days and if
your topic is applicable to more than one dev-room, you are welcome
to make more than one submission.  Please contact us or put a note in
the memo field at the top of the talk proposal if you do that.

All projects are encouraged to consider making a lightning talk too,
it is an excellent opportunity to get exposure for your project:
even though you only have 15 minutes, it can be a much larger and more
diverse audience than in some dev-rooms.

For full details, please see the original call for participation:
https://danielpocock.com/fosdem-2017-rtc-cfp

We invite all potential speakers and participants to discuss the selection 
process and other aspects of FOSDEM on the Free-RTC mailing list:
https://lists.fsfe.org/mailman/listinfo/free-rtc

[Jwchat-devel] [CFP] FOSDEM 2017, RTC devroom, speakers, volunteers neeeded

[FOSDEM R. T. <fos...@fr...>]

FOSDEM is one of the world's premier meetings of free software developers,
with over five thousand people attending each year.  FOSDEM 2017
takes place 4-5 February 2017 in Brussels, Belgium.  https://fosdem.org

This email contains information about:
- Real-Time communications dev-room and lounge,
- speaking opportunities,
- volunteering in the dev-room and lounge,
- related events around FOSDEM, including the XMPP summit,
- social events (the legendary FOSDEM Beer Night and Saturday night dinners
    provide endless networking opportunities),
- the Planet aggregation sites for RTC blogs

Call for participation - Real Time Communications (RTC)
=======================================================

The Real-Time dev-room and Real-Time lounge is about all things involving
real-time communication, including: XMPP, SIP, WebRTC, telephony,
mobile VoIP, codecs, peer-to-peer, privacy and encryption.  The dev-room
is a successor to the previous XMPP and telephony dev-rooms.
We are looking for speakers for the dev-room and volunteers and
participants for the tables in the Real-Time lounge.

The dev-room is only on Saturday, 4 February 2017.  The lounge will
be present for both days.

To discuss the dev-room and lounge, please join the FSFE-sponsored
Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc

To be kept aware of major developments in Free RTC, without being on the
discussion list, please join the Free-RTC Announce list:
http://lists.freertc.org/mailman/listinfo/announce

Speaking opportunities
----------------------

Note: if you used FOSDEM Pentabarf before, please use the same account/username

Real-Time Communications dev-room: deadline 23:59 UTC on 17 November.
Please use the Pentabarf system to submit a talk proposal for the
dev-room.  On the "General" tab, please look for the "Track" option and
choose "Real-Time devroom".  https://penta.fosdem.org/submission/FOSDEM17/

Other dev-rooms and lightning talks: some speakers may find their topic is
in the scope of more than one dev-room.  It is encouraged to apply to more
than one dev-room and also consider proposing a lightning talk, but please
be kind enough to tell us if you do this by filling out the notes in the form.
You can find the full list of dev-rooms at
   https://www.fosdem.org/2017/schedule/tracks/
and apply for a lightning talk at https://fosdem.org/submit

Main track: the deadline for main track presentations is 23:59 UTC
31 October.  Leading developers in the Real-Time Communications
field are encouraged to consider submitting a presentation to
the main track at https://fosdem.org/submit

First-time speaking?
--------------------

FOSDEM dev-rooms are a welcoming environment for people who have never
given a talk before.  Please feel free to contact the dev-room administrators
personally if you would like to ask any questions about it.

Submission guidelines
---------------------

The Pentabarf system will ask for many of the essential details.  Please
remember to re-use your account from previous years if you have one.

In the "Submission notes", please tell us about:
- the purpose of your talk
- any other talk applications (dev-rooms, lightning talks, main track)
- availability constraints and special needs

You can use HTML and links in your bio, abstract and description.

If you maintain a blog, please consider providing us with the
URL of a feed with posts tagged for your RTC-related work.

We will be looking for relevance to the conference and dev-room themes,
presentations aimed at developers of free and open source software about
RTC-related topics.

Please feel free to suggest a duration between 20 minutes and 55 minutes
but note that the final decision on talk durations will be made by the
dev-room administrators.  As the two previous dev-rooms have been
combined into one, we may decide to give shorter slots than in previous
years so that more speakers can participate.

Please note FOSDEM aims to record and live-stream all talks.
The CC-BY license is used.

Volunteers needed
=================

To make the dev-room and lounge run successfully, we are looking for
volunteers:

- FOSDEM provides video recording equipment and live streaming,
  volunteers are needed to assist in this
- organizing one or more restaurant bookings (dependending upon number of
  participants) for the evening of Saturday, 4 February
- participation in the Real-Time lounge
- helping attract sponsorship funds for the dev-room to pay for the
  Saturday night dinner and any other expenses
- circulating this Call for Participation to other mailing lists

See the mailing list discussion for more details about volunteering:
https://lists.fsfe.org/pipermail/free-rtc/2016-October/000285.html

Related events - XMPP and RTC summits
=====================================

The XMPP Standards Foundation (XSF) has traditionally held a summit
in the days before FOSDEM.  There is discussion about a similar
summit taking place on 2 and 3 February 2017
http://wiki.xmpp.org/web/Summit_21 - please join the mailing
list for details: http://mail.jabber.org/mailman/listinfo/summit

We are also considering a more general RTC or telephony summit,
potentially in collaboration with the XMPP summit.
Please join the Free-RTC mailing list and send an email if you would
be interested in participating, sponsoring or hosting such an event.

Social events and dinners
=========================

The traditional FOSDEM beer night occurs on Friday, 3 February.

On Saturday night, there are usually dinners associated with
each of the dev-rooms.  Most restaurants in Brussels are not so
large so these dinners have space constraints and reservations are
essential.  Please subscribe to the Free-RTC mailing list for
further details about the Saturday night dinner options and how
you can register for a seat: https://lists.fsfe.org/mailman/listinfo/free-rtc

Spread the word and discuss
===========================

If you know of any mailing lists where this CfP would be relevant, please
forward this email. If this dev-room excites you, please blog or microblog
about it, especially if you are submitting a talk.

If you regularly blog about RTC topics, please send details about your
blog to the planet site administrators:

  All projects    http://planet.freertc.org       pl...@fr...

  XMPP            http://planet.jabber.org        ra...@ik...

  SIP             http://planet.sip5060.net       pl...@si...
    (Español)     http://planet.sip5060.net/es/   pl...@si...

Please also link to the Planet sites from your own blog or web site as
this helps everybody in the free real-time communications community.

Contact
=======

For any private queries, contact us directly using the address 
fos...@fr... and for any other queries please ask on
the Free-RTC mailing list:
https://lists.fsfe.org/mailman/listinfo/free-rtc

The dev-room administration team:

  Saúl Ibarra Corretgé <sa...@gm...>
  Iain R. Learmonth <ir...@de...>
  Ralph Meijer <ra...@ik...>
  Daniel-Constantin Mierla <mi...@gm...>
  Daniel Pocock <da...@po...>

[Jwchat-devel] URL for guest account auto-login into conference

[Martin V. <mar...@ao...>]

Hello,

I know how to auto-login a guest account:

  https://im.mydomain.com/index.html?jid=guest

Can I similarly auto-login a guest account into an existing conference
(chat room) ?

I can log in to the conference "manually", by first logging into jwchat
and then clicking on "Join Groupchat". Once in, I can see the following
URL in the adresss bar:

https://im.mydomain.com/groupchat.html?jid=con...@mu...&nick=guest&pass=

But that URL does not auto-login me into the chat, if I paste it into my
browsers address bar.

I would like to have a URL, which I can send out to a (unsophisticated
user) to make login for him as simple as possible, so that he does not
need to click through the intermediary steps.

Is this possible ?

Cheers,
Martin

[Jwchat-devel] Issue with configuring jwchat

[Sujith H <har...@gm...>]

Hi all,

I am a newbie to jwchat. I wanted to configure jwchat to make it work with
jabberd2. Hence
I found punjab, which has BOSH support. I configured punjab. Hence the port
5280 port is
open in my pc. Now I had added an .htaccess file in the /var/ww/jwchat
directory as:

AddDefaultCharset UTF-8
Options +MultiViews
<IfModule mod_rewrite.c>
        RewriteEngine On
        RewriteRule http-poll/ http://jabber.mycompany.com:5280/http-poll/ [P]
</IfModule>

The port 5222 of jabberd2 is also open. When I open http://localhost/jwchat
I am able to see the jwchat UI. Now the issue is that I am not able to add
a new user in the Native Binding mode/Poll. Can anyone help me how to do it?


Sujith H

Re: [Jwchat-devel] load testing jwchat

[Artur H. <aj...@ti...>]

Ah,

So you look for a way to run load tests with jwchat not
on jwchat :-)

I have run similar tests on the Tigase server some time ago:
http://www.tigase.org/en/150k-load-tests

I used for this my own project: Tigase Test Suite
which can mimic many connected clients:
http://www.tigase.org/en/content/tigase-test-suite

I am not sure it this suits you. In theory it should work
with any XMPP server but some tests scripts are
dedicated for the Tigase specifics. So some effort would
be needed to use it for testing different server.

If you want to test Tigase I could help you with setting
tests up.

Artur

On 3 Dec 2008, at 00:20, Sean Dilda wrote:

> Artur Hefczyc wrote:
>> Hi,
>>
>> On 2 Dec 2008, at 22:23, Sean Dilda wrote:
>>
>>> Does anyone have any experience load testing jwchat?
>>
>> What you mean by "load testing jwchat"?
>> This is a client, web client isn't it?
>>
>> How would you like to run load tests on the client and
>> what for?
>>
>
> I want to verify that apache can handle a large number of open proxy
> connections without a problem.  I'd also like to verify that ejabberd
> can handle that many http bind connections.  I'd also like to make  
> sure
> that the application as a whole stays responsive with that many
> connections open.
>
> I am thus looking for something that'll let me open a couple thousand
> connections through jwchat (or mimicing the way jwchat works), login  
> and
> send messages to each other so that I can say that I know the
> application will handle the load before we make it production.
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> JWChat-devel mailing list
> JWC...@li...
> https://lists.sourceforge.net/lists/listinfo/jwchat-devel

Artur
-- 
Artur Hefczyc
http://www.tigase.org/
http://artur.hefczyc.net/

Re: [Jwchat-devel] load testing jwchat

[Sean D. <se...@du...>]

Artur Hefczyc wrote:
> Hi,
> 
> On 2 Dec 2008, at 22:23, Sean Dilda wrote:
> 
>> Does anyone have any experience load testing jwchat?
> 
> What you mean by "load testing jwchat"?
> This is a client, web client isn't it?
> 
> How would you like to run load tests on the client and
> what for?
> 

I want to verify that apache can handle a large number of open proxy 
connections without a problem.  I'd also like to verify that ejabberd 
can handle that many http bind connections.  I'd also like to make sure 
that the application as a whole stays responsive with that many 
connections open.

I am thus looking for something that'll let me open a couple thousand 
connections through jwchat (or mimicing the way jwchat works), login and 
send messages to each other so that I can say that I know the 
application will handle the load before we make it production.

Re: [Jwchat-devel] load testing jwchat

[Artur H. <aj...@ti...>]

Hi,

On 2 Dec 2008, at 22:23, Sean Dilda wrote:

> Does anyone have any experience load testing jwchat?

What you mean by "load testing jwchat"?
This is a client, web client isn't it?

How would you like to run load tests on the client and
what for?

Artur
-- 
Artur Hefczyc
http://www.tigase.org/
http://artur.hefczyc.net/

[Jwchat-devel] load testing jwchat

[Sean D. <se...@du...>]

Does anyone have any experience load testing jwchat?


I'm being asked to do a production deployment of jwchat and as part of 
that I need to find a way to load test it.  If anyone has any examples 
of how they've load tested it, I'd love to hear them.


Thanks,


Sean

[Jwchat-devel] jwchat: search feature

[loulou2u <mc...@so...>]

Anyone know how to customize the search.html file. I tried adding another
option list to include an additional directory to search under but while I
am able to view the change accessing the search.html directly, when I go to
the page through the chat client none of my changes appear.

I would love to add additional search capabilities.

Thanks

Laura
-- 
View this message in context: http://www.nabble.com/jwchat%3A-search-feature-tp20802131p20802131.html
Sent from the jwchat-devel mailing list archive at Nabble.com.

Re: [Jwchat-devel] JWChat timeout/heartbeat issues

[Liz W. <li...@du...>]

Dear Stefan,

You are absolutely right, setting the timeout of the client to less than 
the apache server solves the problem.  In retrospect that seems so 
obvious. :) 

Thanks so much for your help and for providing such a terrific application,

-- 
Liz Wendland
Duke University Office of Information Technology




Stefan Strigler wrote:
> Hi Liz,
>
> please either increase the value for "Timeout" at your apache to sth  
> like 330 or such.
>
> Or adjust JSJACHBC_MAX_WAIT at jsjac.js to sth like 280 or such.
>
> Cheers, Steve
>
>
> Am 26.11.2008 um 16:45 schrieb Liz Wendland:
>
>   
>> Hi,
>>
>> We are using the following setup:
>> * JWChat (with latest jsjac lib from SVN - thanks for the ff3 fix!)
>> * Ejabberd (using its built-in http-bind)
>> * Apache/2.2.9
>>
>> Things seem to work marvelously, but we see errors every 5 minutes in
>> our Apache log about timeouts:
>>
>> (70007)The timeout specified has expired: proxy: error reading status
>> line from remote server 127.0.0.1
>>
>> Looking at the ejabberd and jwchat debug logs we can see JWChat and
>> Ejabberd reconnect after this. Users see no problems. After the 10th
>> reconnect their jabber session fails. At that point JWChat gives up
>> (having exceeded JSJAC_ERR_COUNT = 10) and doesn't automatically  
>> reconnect.
>>
>> 5 minutes is the amount of time for the Apache Timeout:
>> #
>> # Timeout: The number of seconds before receives and sends time out.
>> #
>> Timeout 300
>>
>> So it seems that Apache doesn't see any activity on the connection and
>> times it out and ends the connection.
>>
>> My Javascript skills are rather poor, but there seems to be some  
>> code in
>> jsjac to do regular "heartbeat" messages, it just is never invoked?   
>> How
>> does a BOSH connection indicate that the client is still alive even if
>> no activity is occurring?
>>
>> Thanks for any help,
>>
>> -- 
>> Liz Wendland
>> Duke University Office of Information Technology
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's  
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win  
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in  
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> JWChat-devel mailing list
>> JWC...@li...
>> https://lists.sourceforge.net/lists/listinfo/jwchat-devel
>>     
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> JWChat-devel mailing list
> JWC...@li...
> https://lists.sourceforge.net/lists/listinfo/jwchat-devel
>   

Re: [Jwchat-devel] JWChat timeout/heartbeat issues

[Stefan S. <st...@ze...>]

Hi Liz,

please either increase the value for "Timeout" at your apache to sth  
like 330 or such.

Or adjust JSJACHBC_MAX_WAIT at jsjac.js to sth like 280 or such.

Cheers, Steve


Am 26.11.2008 um 16:45 schrieb Liz Wendland:

> Hi,
>
> We are using the following setup:
> * JWChat (with latest jsjac lib from SVN - thanks for the ff3 fix!)
> * Ejabberd (using its built-in http-bind)
> * Apache/2.2.9
>
> Things seem to work marvelously, but we see errors every 5 minutes in
> our Apache log about timeouts:
>
> (70007)The timeout specified has expired: proxy: error reading status
> line from remote server 127.0.0.1
>
> Looking at the ejabberd and jwchat debug logs we can see JWChat and
> Ejabberd reconnect after this. Users see no problems. After the 10th
> reconnect their jabber session fails. At that point JWChat gives up
> (having exceeded JSJAC_ERR_COUNT = 10) and doesn't automatically  
> reconnect.
>
> 5 minutes is the amount of time for the Apache Timeout:
> #
> # Timeout: The number of seconds before receives and sends time out.
> #
> Timeout 300
>
> So it seems that Apache doesn't see any activity on the connection and
> times it out and ends the connection.
>
> My Javascript skills are rather poor, but there seems to be some  
> code in
> jsjac to do regular "heartbeat" messages, it just is never invoked?   
> How
> does a BOSH connection indicate that the client is still alive even if
> no activity is occurring?
>
> Thanks for any help,
>
> -- 
> Liz Wendland
> Duke University Office of Information Technology
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> JWChat-devel mailing list
> JWC...@li...
> https://lists.sourceforge.net/lists/listinfo/jwchat-devel

[Jwchat-devel] JWChat timeout/heartbeat issues

[Liz W. <li...@du...>]

Hi,
 
We are using the following setup:
* JWChat (with latest jsjac lib from SVN - thanks for the ff3 fix!)
* Ejabberd (using its built-in http-bind)
* Apache/2.2.9 
 
Things seem to work marvelously, but we see errors every 5 minutes in 
our Apache log about timeouts:
 
(70007)The timeout specified has expired: proxy: error reading status 
line from remote server 127.0.0.1
 
Looking at the ejabberd and jwchat debug logs we can see JWChat and 
Ejabberd reconnect after this. Users see no problems. After the 10th 
reconnect their jabber session fails. At that point JWChat gives up 
(having exceeded JSJAC_ERR_COUNT = 10) and doesn't automatically reconnect.
 
5 minutes is the amount of time for the Apache Timeout:
#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300
 
So it seems that Apache doesn't see any activity on the connection and 
times it out and ends the connection.
 
My Javascript skills are rather poor, but there seems to be some code in 
jsjac to do regular "heartbeat" messages, it just is never invoked?  How 
does a BOSH connection indicate that the client is still alive even if 
no activity is occurring?
 
Thanks for any help,

-- 
Liz Wendland
Duke University Office of Information Technology

Re: [Jwchat-devel] A couple problems with jwchat.

[Stefan S. <st...@ze...>]

Hi,


Am Freitag, den 21.11.2008, 11:41 -0500 schrieb Sean Dilda:
> > I've filed a bug report at
> > https://trac.stefan-strigler.de/jsjac/ticket/46 and I'll try to fix it
> > ASAP.
> > 
> 
> This link doesn't seem to work anymore.  Does anyone know what the 
> status of this bug is?

The URL has changed, it's https://trac.jwchat.org/jsjac/ticket/46 now.
But I'll try to make redirects work again.

Btw the Bug is fixed at rev474 but there's no new release yet.

Cheers, Steve

Re: [Jwchat-devel] A couple problems with jwchat.

[Sean D. <se...@du...>]

Stefan Strigler wrote:
> Hi,
> 
> Am Mittwoch, den 16.07.2008, 14:10 -0400 schrieb Sean Dilda:
> 
> [...]
> 
>> The key difference seems to be that with FF3, the body tag (inside the 
>> message tag) is setting 'xmlns=""'.  In FF2 it isn't doing that.
>>
>> I mimiced this difference using the XMPP console in pidgin and found 
>> that ejabberd quietly passes the message on, but pidgin ignores the 
>> incoming message that has the xmlns set in the body tag.
> 
> Oh I see. Thanks for tracing this down. This is a major problem then. 
> 
> I've filed a bug report at
> https://trac.stefan-strigler.de/jsjac/ticket/46 and I'll try to fix it
> ASAP.
> 

This link doesn't seem to work anymore.  Does anyone know what the 
status of this bug is?

[Jwchat-devel] jwchat search options

[Laura M. <mc...@so...>]

I'm wondering if there is anyone out that that has implemented an ldap
directory (or any directory) to the  'Open Search' feature? First of
all, I noticed that when I try to add an option in the search.html file
my option does not appear at all. Is there another file that should be
revised other than the search.html?

Thanks,
 Laura

-- 
Laura McCord
Web Programmer/Analyst
Information Technology Services
Southwestern University
512/863-1066
mc...@so...

Re: [Jwchat-devel] Can't get jwchat working via https

[Laura M. <mc...@so...>]

Thanks for the response. I finally got it to work using the port 5222 as
stated in the ejabberd instructions. It turned out that my Apache
configuration file was not setup to listen on that port.

Thanks,
 Laura

Sean Dilda wrote:
> Laura McCord wrote:
>   
>> I had jwchat working without using ssl but I had ssl installed and now I
>> can't get jwchat working. Is there some further configuring that needs
>> to be done to get jwchat working or is this a ejabberd issue?
>>
>>     
>
>
> Where are you trying to do ssl?
>
> If you're doing SSL between the browser and apache, then non-ssl from 
> apache to ejabberd, then it should work.   If you are trying to do SSL 
> to ejabberd, then that's a known bug.  However, a 'temporary solution' 
> was applied to ejabberd svn for that earlier today.  See 
> https://support.process-one.net/browse/EJAB-507
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> JWChat-devel mailing list
> JWC...@li...
> https://lists.sourceforge.net/lists/listinfo/jwchat-devel
>   


-- 
Laura McCord
Web Programmer/Analyst
Information Technology Services
Southwestern University
512/863-1066
mc...@so...

Re: [Jwchat-devel] Can't get jwchat working via https

[Sean D. <se...@du...>]

Laura McCord wrote:
> I had jwchat working without using ssl but I had ssl installed and now I
> can't get jwchat working. Is there some further configuring that needs
> to be done to get jwchat working or is this a ejabberd issue?
> 


Where are you trying to do ssl?

If you're doing SSL between the browser and apache, then non-ssl from 
apache to ejabberd, then it should work.   If you are trying to do SSL 
to ejabberd, then that's a known bug.  However, a 'temporary solution' 
was applied to ejabberd svn for that earlier today.  See 
https://support.process-one.net/browse/EJAB-507

[Jwchat-devel] Can't get jwchat working via https

[Laura M. <mc...@so...>]

I had jwchat working without using ssl but I had ssl installed and now I
can't get jwchat working. Is there some further configuring that needs
to be done to get jwchat working or is this a ejabberd issue?

Thanks,
    Laura

-- 
Laura McCord
Web Programmer/Analyst
Information Technology Services
Southwestern University
512/863-1066
mc...@so...

Re: [Jwchat-devel] A couple problems with jwchat.

[Stefan S. <st...@ze...>]

Thanks a lot. I've commited your patch to jwchat's CVS repository.

Cheers, Steve

Am Donnerstag, den 17.07.2008, 13:06 -0400 schrieb Sean Dilda:
> Stefan Strigler wrote:
> 
> >> Thanks.  I'll just patch my copy to remove those lines then.   I can 
> >> send you a copy of the patch if you like, although its a pretty basic 
> >> change.
> > 
> > Sure, if you could send me a patch (against latest from CVS) that'd be
> > great. Saves me some work.
> >
> 
> 
> The patch is attached.
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________ JWChat-devel mailing list JWC...@li... https://lists.sourceforge.net/lists/listinfo/jwchat-devel

Re: [Jwchat-devel] A couple problems with jwchat.

[Sean D. <se...@du...>]

Stefan Strigler wrote:

>> Thanks.  I'll just patch my copy to remove those lines then.   I can 
>> send you a copy of the patch if you like, although its a pretty basic 
>> change.
> 
> Sure, if you could send me a patch (against latest from CVS) that'd be
> great. Saves me some work.
>


The patch is attached.

Re: [Jwchat-devel] A couple problems with jwchat.

[Stefan S. <st...@ze...>]

Hi,

Am Mittwoch, den 16.07.2008, 14:10 -0400 schrieb Sean Dilda:

[...]

> The key difference seems to be that with FF3, the body tag (inside the 
> message tag) is setting 'xmlns=""'.  In FF2 it isn't doing that.
> 
> I mimiced this difference using the XMPP console in pidgin and found 
> that ejabberd quietly passes the message on, but pidgin ignores the 
> incoming message that has the xmlns set in the body tag.

Oh I see. Thanks for tracing this down. This is a major problem then. 

I've filed a bug report at
https://trac.stefan-strigler.de/jsjac/ticket/46 and I'll try to fix it
ASAP.

> Thanks.  I'll just patch my copy to remove those lines then.   I can 
> send you a copy of the patch if you like, although its a pretty basic 
> change.

Sure, if you could send me a patch (against latest from CVS) that'd be
great. Saves me some work.

Cheers, 

Steve

Re: [Jwchat-devel] A couple problems with jwchat.

[Sean D. <se...@du...>]

Stefan Strigler wrote:
> Sean,
> 
> Am Mittwoch, den 16.07.2008, 09:56 -0400 schrieb Sean Dilda:
> 
>> The first problem is that when I open a chat window and type into it, 
>> the recipient never receives the IM.  This seems to work in some cases, 
>> but not others.  The place I can consistently get it to fail is using 
>> Firefox 3 as my browser on Linux (CentOS 5 specifically).  Does anyone 
>> know how to resolve this issue?
> 
> Sorry, don't know what could be the problem here. Did you try turning on
> debugging or checking the actual network traffic? Firebug is a good
> extension for Firefox to track down such problems btw.

I did a tcpdump between apache and ejabberd.  This is what I found:

 From FF3:

<body rid='622713' sid='cb299709563672ae8bc7029ecd56f7f803fb065c' 
xmlns='http://jabber.org/protocol/httpbind' 
key='436543e9f153c5c93c30001162640c0dff7e9944' ><message 
xmlns="jabber:client" type="chat" to="XX...@gm..."><body 
xmlns="">test</body></message></body>

 From FF2:

<body rid='662313' sid='bbc2d1ec433ef298f546bc9ecd37a471bad0125e' 
xmlns='http://jabber.org/protocol/httpbind' 
key='5494dff971ceb080dd8cf28b132ba4089b342fff' ><message 
xmlns="jabber:client" type="chat" 
to="XX...@gm..."><body>test</body></message></body>


The key difference seems to be that with FF3, the body tag (inside the 
message tag) is setting 'xmlns=""'.  In FF2 it isn't doing that.

I mimiced this difference using the XMPP console in pidgin and found 
that ejabberd quietly passes the message on, but pidgin ignores the 
incoming message that has the xmlns set in the body tag.

> 
>> The other problem is I keep getting 404 errors in my logs for the file 
>> 'xmlextras.js'.  Is this a bug in that jwchat is asking for the file? 
>> Or am I missing a file that needs to be installed?
> 
> The file doesn't exist anymore as of latestest versions of jsjac. But
> obviously it's still referenced somewhere within jwchat. But actually
> that's nothing to worry about.
> 

Thanks.  I'll just patch my copy to remove those lines then.   I can 
send you a copy of the patch if you like, although its a pretty basic 
change.

Re: [Jwchat-devel] A couple problems with jwchat.

[Stefan S. <st...@ze...>]

Sean,

Am Mittwoch, den 16.07.2008, 09:56 -0400 schrieb Sean Dilda:

> The first problem is that when I open a chat window and type into it, 
> the recipient never receives the IM.  This seems to work in some cases, 
> but not others.  The place I can consistently get it to fail is using 
> Firefox 3 as my browser on Linux (CentOS 5 specifically).  Does anyone 
> know how to resolve this issue?

Sorry, don't know what could be the problem here. Did you try turning on
debugging or checking the actual network traffic? Firebug is a good
extension for Firefox to track down such problems btw.

> The other problem is I keep getting 404 errors in my logs for the file 
> 'xmlextras.js'.  Is this a bug in that jwchat is asking for the file? 
> Or am I missing a file that needs to be installed?

The file doesn't exist anymore as of latestest versions of jsjac. But
obviously it's still referenced somewhere within jwchat. But actually
that's nothing to worry about.

Cheers, Steve

[Jwchat-devel] A couple problems with jwchat.

[Sean D. <se...@du...>]

I'm currently working on setting up jwchat for our environment, but I"m 
running into a few problems.

I'm using apache 2.2 and ejabberd 2.0.1.  These are problems I first saw 
with jwchat 1.0beta3, so I upgraded to CVS on July 14 and I'm still 
seeing the same problems.

The first problem is that when I open a chat window and type into it, 
the recipient never receives the IM.  This seems to work in some cases, 
but not others.  The place I can consistently get it to fail is using 
Firefox 3 as my browser on Linux (CentOS 5 specifically).  Does anyone 
know how to resolve this issue?

The other problem is I keep getting 404 errors in my logs for the file 
'xmlextras.js'.  Is this a bug in that jwchat is asking for the file? 
Or am I missing a file that needs to be installed?


Thanks,


Sean