Provider specific functionality

[Nikita Kalashnikov]

Hi,

I'm not sure if this issue has been addressed or not, I'm a newcomer
to this group so apologies if this was answered already. A quick
search didn't turn anything up though. Is there any consensus on how
to cleanly integrate provider specific functionality into the SDKs?
Although the 0.9 standard encompasses a fair swath of functionality,
obviously there will always be something provider specific for each
platform.

Nikita

[Jason (Google)]

Hi Nikita. One thing that we're doing on the Java side is adding provider-specific services (e.g. MySpace's StatusMood service) in separate packages, e.g.:

http://code.google.com/p/opensocial-java-client/source/browse/#svn/trunk/java/src/org/opensocial/services/myspace

The Provider classes also provide preRequest and postRequest methods for provider-specific request tailoring:

http://code.google.com/p/opensocial-java-client/source/browse/trunk/java/src/org/opensocial/providers/MySpaceProvider.java

- Jason

--

You received this message because you are subscribed to the Google Groups "opensocial-client-libraries" group.
To post to this group, send email to opensocial-cl...@googlegroups.com.
To unsubscribe from this group, send email to opensocial-client-l...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opensocial-client-libraries?hl=en.

[Nikita Kalashnikov]

I see, so looks like the convention is simply creating appropriate
model/service classes within provider specific folders?

Nikita

On Dec 10, 2:15 pm, "Jason (Google)" <apija...@google.com> wrote:
> Hi Nikita. One thing that we're doing on the Java side is adding
> provider-specific services (e.g. MySpace's StatusMood service) in separate
> packages, e.g.:
>

> http://code.google.com/p/opensocial-java-client/source/browse/#svn/tr...

>
> The Provider classes also provide preRequest and postRequest methods for
> provider-specific request tailoring:
>

> http://code.google.com/p/opensocial-java-client/source/browse/trunk/j...

>
> - Jason
>
> On Thu, Dec 10, 2009 at 2:01 PM, Nikita Kalashnikov <
>

> nikita.kalashni...@gmail.com> wrote:
> > Hi,
>
> > I'm not sure if this issue has been addressed or not, I'm a newcomer
> > to this group so apologies if this was answered already. A quick
> > search didn't turn anything up though. Is there any consensus on how
> > to cleanly integrate provider specific functionality into the SDKs?
> > Although the 0.9 standard encompasses a fair swath of functionality,
> > obviously there will always be something provider specific for each
> > platform.
>
> > Nikita
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "opensocial-client-libraries" group.
> > To post to this group, send email to
> > opensocial-cl...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > opensocial-client-l...@googlegroups.com<opensocial-client-libraries%2Bunsu...@googlegroups.com>
> > .

[Jason (Google)]

This is the direction we've chosen for Java. Other libraries do this differently, e.g. the PHP library doesn't have a separate package for the MySpace-specific services:

http://code.google.com/p/opensocial-php-client/source/browse/#svn/trunk/src/osapi/service

- Jason

On Thu, Dec 10, 2009 at 2:38 PM, Jason Cooper <jasona...@google.com> wrote:

This is the direction we've chosen for Java. Other libraries do this differently, e.g. the PHP library doesn't have a separate package for the MySpace-specific services:

http://code.google.com/p/opensocial-php-client/source/browse/#svn/trunk/src/osapi/service

- Jason

To unsubscribe from this group, send email to opensocial-client-l...@googlegroups.com.