Yes, we had a project that was registering CORBA IORs that ran to over 3000
bytes, and had a similar problem.

Someone suggested, as a "quick fix" that we change the SLP_MAX_DATAGRAM_SIZE
macro as follows:
        #define SLP_MAX_DATAGRAM_SIZE  SLPPropertyAsInteger("net.slp.MTU")
so we could control the MTU via the config file.

As the macro is never used in a compile-time only context (eg. as the size
of an array), and the SLPPropertyAsInteger call works in both the client
library and the daemon code, this worked for that situation.  However, I
wasn't happy about it in a general sense, so I didn't make the change in the
OpenSLP code (we apply it as a patch when building).  I haven't had the time
to do a proper job along the lines of that proposed by Venkat Puvvada (but
extended to cover all the references to SLP_MAX_DATAGRAM_SIZE in both daemon
and library code).

We would certainly support such a fix.

Regards,

Richard Morrell

-----Original Message-----
From: Varun Chandramohan [mailto:var...@linux.vnet.ibm.com]
Sent: 07 July 2010 20:59
To: Morrell Richard (external)
Cc: 'openslp-devel@lists.sourceforge.net'; John Calcote
Subject: Fwd: Re: Regd: Openslp MTU issue


To take is discussion forward. This sounds like a important issue to me and
we can work on a fix if the fix currently provided is right approach.

Richard, any thoughts?

This email, including any attachment, is a confidential communication
intended solely for the use of the individual or entity to whom it is
addressed. It contains information which is private and may be proprietary
or covered by legal professional privilege. If you have received this email
in error, please notify the sender upon receipt, and immediately delete it
from your system.

Anything contained in this email that is not connected with the businesses
of this company is neither endorsed by nor is the liability of this company.

Whilst we have taken reasonable precautions to ensure that any attachment to
this email has been swept for viruses, we cannot accept liability for any
damage sustained as a result of software viruses, and would advise that you
carry out your own virus checks before opening any attachment.


------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Openslp-devel mailing list
Openslp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openslp-devel

Reply via email to