It really depends how you are writing your your plugins... and I use
the term plug ins loosely. For example you could launch a pluggin from
an actual Red Dot page itself and pass the session/login guid in the
query string. If you want to embed the plugin in the action menu but
use php in theory you can write an ASP wrapper to pass the required
information via the query string. Other things I've done is actually
login to reddot with a user account via RQL do what ever I need to do
and log out, you can create a separate user account just for plugins
and increase the session limits there is still potential you'll run
into collisions once in a blue moon. I'll try an clean up the php
login bridge for you this weekend.

On May 28, 11:33 am, William Shen <[email protected]> wrote:
> We're using ASP.NET and Java to handle RQL via webserive out side RedDot But
> some time, we have to "hack" the database to fetch existed session key(just
> query user's session key from database directly)
>
> 2009/5/28 butabi <[email protected]>
>
>
>
> > you could try something like this (just a guess):
>
> > require_once(file_with_php_rqlbridge_class.php);
> > $rb = new RQLBridge();
> > $rb->xmlQuery = '<IODATA sessionkey=... your xml stuff ...</IODATA>';
> > $rb->sendXML();
>
> > On 26 Mai, 12:21, abdn_webteam <[email protected]> wrote:
> > > The above code is, I'm sure, very helpful to those who know Object
> > > Oriented Programming, but for those of us who are less familiar with
> > > OOP is there any chance you could explain how to use your class above,
> > > especially when passing and retrieving values?
>
> --
> Best Regards
> William Shen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"RedDot CMS Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/RedDot-CMS-Users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to