I was originally thinking that someone implementing this could just set a
slp.conf setting to prefer sending v1, but your way would be more flexible.
As another possibility, while it would be nice to be able to send v1 in
openslp, we might be able to solve the problem faster with something that
already exists. Ramakrishnan, is your host software that does slpv1
proprietary?
--Nick
On Thu, Sep 15, 2011 at 11:29 AM, John Calcote <john.calc...@gmail.com>wrote:
> Nick,****
>
> ** **
>
> I don’t know of a client that already does this. I think probably the
> simplest, least intrusive way would be to set an attribute on an open handle
> that tells the library to try to use v1 request format, if possible. Since
> there isn’t a reasonably generic “flags” word that can be hijacked in the
> SLPOpen function, we should probably create a new interface function that
> sets a USE_SLPv1_REQUESTS flag on an open handle:****
>
> ** **
>
> #define USE_SLPv1_REQUESTS 0x01****
>
> ** **
>
> SLPEXP SLPError SLPAPI SLPSetHandleAttributes(****
>
> SLPHandle hSLP, ****
>
> unsigned flags, ****
>
> ... );****
>
> ** **
>
> If we use a variadic interface like this, the variable argument list can be
> determined by the requirements of the flags passed – some flags wouldn’t
> need additional arguments (like this one). That way we can extend this
> function easily by adding new flags values and defining the remaining
> arguments (if any) that are required by the flag at the time the flag is
> defined. Flags can be OR’d together, and required additional arguments are
> passed in flag definition order.****
>
> ** **
>
> Once we have the ability to add such suggestive attributes to an open
> handle, we can then implement v1 request functionality for one function at a
> time, as needed, starting with an attribute request. We’ll use it for
> testing, but it enhances the entire interface really, because I can see a
> customer (such as Ram) wanting to make v1 requests (if possible) for
> whatever reason.****
>
> ** **
>
> Finally, we can enhance the slptool to accept a new command line argument
> that indicates it should try to use v1 requests.****
>
> ** **
>
> Thoughts? Is this overkill?****
>
> ** **
>
> John****
>
> ** **
>
> *From:* nwagner...@gmail.com [mailto:nwagner...@gmail.com] *On Behalf Of *Nick
> Wagner
> *Sent:* Wednesday, September 14, 2011 8:31 PM
> *To:* John Calcote
> *Cc:* Ramakrishnan s; openslp-users@lists.sourceforge.net
>
> *Subject:* Re: [Openslp-users] SLPv1 support****
>
> ** **
>
> Agreed. Silly question -- what's the easiest way to send a SLPv1 request?
> ****
>
> ** **
>
> --Nick****
>
> On Wed, Sep 14, 2011 at 1:01 PM, John Calcote <john.calc...@gmail.com>
> wrote:****
>
> That would be a good bug to fix.****
>
> ****
>
> *From:* Ramakrishnan s [mailto:rama_krishn...@hotmail.com]
> *Sent:* Wednesday, September 14, 2011 10:41 AM
> *To:* ne...@wingedbeast.org
> *Cc:* openslp-users@lists.sourceforge.net****
>
>
> *Subject:* Re: [Openslp-users] SLPv1 support****
>
> ****
>
> Initially I used OpenSLP2.0 beta. When I used OpenSLP 2.0, it was replying
> to Service attribute request, but when I analysed the service attribute
> reply packet, its size was 4096 bytes. After 16 bytes of SLP header, rest of
> of the bytes were filled with zeros. I didn't debug what was causing that
> issue. ****
>
> ****
>
> --Ram****
>
> ****
> ------------------------------
>
> Date: Tue, 13 Sep 2011 09:33:08 -0500
> Subject: Re: [Openslp-users] SLPv1 support
> From: ne...@wingedbeast.org
> To: rama_krishn...@hotmail.com
> CC: openslp-users@lists.sourceforge.net
>
> Does the OpenSLP 2.0 beta code work for you?****
>
> On Tue, Sep 13, 2011 at 3:48 AM, Ramakrishnan s <
> rama_krishn...@hotmail.com> wrote:****
>
> Hi Nick,****
>
> ****
>
> I made sure that ENABLE_SLPv1 is turned on. I have only tried with SLP v1
> attribute request. I stepped through the code and saw
> that SLPv1ProcessMessage() function returns SLP_ERROR_VER_NOT_SUPPORTED.
> When I sniffed the packets, i don't see any response sent by OpenSLP after
> receiving the service attribute request. I have not enabled DA functionality
> as I only require SA functionality. ****
>
> ****
>
> I am using OpenSLP version 1.2.1 (openslpp-1.2.1.tar.gz).****
>
> ****
>
> Thanks for the help.****
>
> ****
>
> -Ram****
>
> ****
> ------------------------------
>
> Date: Mon, 12 Sep 2011 09:49:18 -0500
> Subject: Re: [Openslp-users] SLPv1 support
> From: ne...@wingedbeast.org
> To: rama_krishn...@hotmail.com
> CC: openslp-users@lists.sourceforge.net****
>
>
>
> From what I can see, the default for the linux build is to enable SLPv1
> support via the ENABLE_SLPv1 preprocessor definition. Is ENABLE_SLPv1
> defined for your build? You said it doesn't respond to attribute requests.
> If you sniff it, do you see it responding to any v1 requests?****
>
> ****
>
> What version are you using?****
>
> ****
>
> --Nick****
>
> On Mon, Sep 12, 2011 at 4:40 AM, Ramakrishnan s <
> rama_krishn...@hotmail.com> wrote:****
>
> Hi,****
>
> ****
>
> I am trying integrate OpenSLP inside my printer FW. Printer FW is running
> on Linux (2.6.32 Kernel). We have a host software that is trying to discover
> printers using SLPv1. During my testing I see that OpenSLP is not replying
> to service attribute requests. From the code it seems to me that the OpenSLP
> does not respond to SLPv1 requests. Is this correct ? Is there a
> configuration or setting through which I can enable SLPv1 ? I was trying
> with OpenSLP version 1.2.1.****
>
> ****
>
> Thanks for the help.****
>
> ****
>
> --Ram****
>
>
>
> ------------------------------------------------------------------------------
> Doing More with Less: The Next Generation Virtual Desktop
> What are the key obstacles that have prevented many mid-market businesses
> from deploying virtual desktops? How do next-generation virtual desktops
> provide companies an easier-to-deploy, easier-to-manage and more affordable
> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
> _______________________________________________
> Openslp-users mailing list
> Openslp-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openslp-users****
>
> ****
>
> ****
>
> ** **
>
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
Openslp-users mailing list
Openslp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openslp-users
